static int graft_tree(struct vfsmount *mnt, struct nameidata *nd)
{
int err;
if (mnt->mnt_sb->s_flags & MS_NOUSER)
return -EINVAL;
Is triggering when I try to mount tmpfs? Is this happening for anybody else?
Shouldn't I be getting a fresh superblock or something? (Is this just a User
Mode Linux issue? Haven't got a spare box set up to boot it on real hardware
just yet...)
If somebody needs a reproduction sequence, I'm happy to oblige. In theory
"mount -t tmpfs /mnt /mnt" should do it, but if it was _that_ simple it
wouldn't have shipped...
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> If somebody needs a reproduction sequence, I'm happy to oblige. In theory
> "mount -t tmpfs /mnt /mnt" should do it, but if it was _that_ simple it
> wouldn't have shipped...
I don't see this behaviour on a regular desktop box running 2.6.14.
Guess it's UML specific.
Jon.
Sorry, but wrong.
IIRC, this triggers when you don't have CONFIG_TMPFS enabled. If you don't,
you still get it, but you get a version that's only usable in-kernel.
Jeff
Yup. Not CONFIG_TEMPFS. My bad.
Rob
That sounds like a regression. Turning off CONFIG_TMPFS replaces tmpfs
with an aliased ramfs. It should be perfectly usable everywhere that
tmpfs is, with the exception that it's not swap-backed and doesn't
have an size limiting.
--
Mathematics is the supreme nostalgia of our time.