The hard coded inode numbers in proc currently limit it'smaintainability, it's flexibility, and what can be done withthe rest of system. /proc limits pid-max to 32768 on 32 bitsystems it limits fd-max to 32768 on all systems, and placingthe pid in the inode number really gets in the way of implementingmultiple pid namespaces.

Ever since people started adding to the middle of the file typeenumeration we haven't been maintaing the historical inode numbers,all we have really succeeded in doing is keeping the pid in the procinode number. The pid is already available in the directory nameso no information is lost removing it from the inode number.

So if something in user space cares if we remove the inode numberfrom the /proc inode it is almost certainly broken.