aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/fs/nilfs2/cpfile.c
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2009-06-14 22:56:48 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2009-06-14 17:58:25 -0700
commit0a8eba9b7f7aa3ad0305627c99ad4d6deedd871d (patch)
treec714028520de3facd053e33abc280dbd214df8fd /fs/nilfs2/cpfile.c
parentMerge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-next (diff)
downloadwireguard-linux-0a8eba9b7f7aa3ad0305627c99ad4d6deedd871d.tar.xz
wireguard-linux-0a8eba9b7f7aa3ad0305627c99ad4d6deedd871d.zip
ramfs: ignore unknown mount options
On systems where CONFIG_SHMEM is disabled, mounting tmpfs filesystems can fail when tmpfs options are used. This is because tmpfs creates a small wrapper around ramfs which rejects unknown options, and ramfs itself only supports a tiny subset of what tmpfs supports. This makes it pretty hard to use the same userspace systems across different configuration systems. As such, ramfs should ignore the tmpfs options when tmpfs is merely a wrapper around ramfs. This used to work before commit c3b1b1cbf0 as previously, ramfs would ignore all options. But now, we get: ramfs: bad mount option: size=10M mount: mounting mdev on /dev failed: Invalid argument Another option might be to restore the previous behavior, where ramfs simply ignored all unknown mount options ... which is what Hugh prefers. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Hugh Dickins <hugh.dickins@tiscali.co.uk> Acked-by: Matt Mackall <mpm@selenic.com> Acked-by: Wu Fengguang <fengguang.wu@intel.com> Cc: stable@kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/nilfs2/cpfile.c')
0 files changed, 0 insertions, 0 deletions