On Fri, 08 Jun 2007 17:43:34 -0600No. You still need my patch to fix the current breakage.
ebiederm@xxxxxxxxxxxx (Eric W. Biederman) wrote:
Some user space tools need to identify SYSV shared memory when
examining /proc/<pid>/maps. To do so they look for a block device
with major zero, a dentry named SYSV<sysv key>, and having the minor of
the internal sysv shared memory kernel mount.
To help these tools and to make it easier for people just browsing
/proc/<pid>/maps this patch modifies hugetlb sysv shared memory to
use the SYSV<key> dentry naming convention.
User space tools will still have to be aware that hugetlb sysv
shared memory lives on a different internal kernel mount and so
has a different block device minor number from the rest of sysv
shared memory.
I assume this fix is preferred over Badari's? If so, why?