Comment 7 for bug 11364

Unfortunately, the kernel registers tmpfs whether CONFIG_TMPFS is
actually enabled or not; this is because mm/shmfs.c and mm/tiny-shmfs.c,
while offering functionality for shm even if CONFIG_TMPFS is unset,
decides to call itself tmpfs. I'm not sure the logic (if there is any)
behind this; I'm betting someone wrote shmfs, then decided it would be
nice to abstract it out into tmpfs.

I don't have any solutions for this right now; probably the "correct"
thing to do would be to split apart tmpfs and shmfs stuff, have
fs/tmpfs*, and have shm depend upon this (and provide its own shmfs
stubs if tmpfs is disabled?).

--
Andres Salomon <email address hidden>