illumos gate

Man, you should have written it down much shorter in order to fit a normal bug description. Ie. start by describing shortly what the issue is, ie: "Disk with rpool on can not be used for other zpools". And then describe how to test it out, and finally how you expect it should work. Writing what could be a normal blog post is not the easiest way to get an overview of what needs fixing.

Replace ?
Disk with rpool should can not be used for other zpools

Normally ,zfs rpool use Slice 0(cXtXdXs0) as the member driver?But "zpool create" allow the disk with rpool (cXtXdXp1) be used for other zpools, it's will make the OS faile to boot next time?and when we do this ,the command will be successful without any confirm or warring!!!
We should add a control ,Disk with rpool should can not be used for other zpools .

Example :
Warring!!! not not try follow command on your production system
@root@egoodbtr-rac1:~# zpool create dpool raidz c8t0d0p1 c8t1d0p1
root@egoodbtr-rac1:~# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
dpool 31.8G 149K 31.7G 0% ONLINE -
rpool 15.9G 4.29G 11.6G 27% ONLINE -
root@egoodbtr-rac1:~# zpool status
pool: dpool
state: ONLINE
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
dpool ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c8t0d0p1 ONLINE 0 0 0
c8t1d0p1 ONLINE 0 0 0

errors: No known data errors

pool: rpool
state: ONLINE
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c8t0d0s0 ONLINE 0 0 0
c8t1d0s0 ONLINE 0 0 0

errors: No known data errors@

This should be done in libdskmgt, and not be specific to ZFS (or any FS), in either case. libdiskmgt is how ZFS notices it's about to clobber an existing filesystem.

I'm not sure if there are complications to noticing if you're about to clobber an FS via a wider, containing, device as here. (does it notice create c0d0 with a filesystem already on c0d0sN?)