[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101023214235.GT19804@ZenIV.linux.org.uk>
Date: Sat, 23 Oct 2010 22:42:35 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: dave@...ux.vnet.ibm.com, akpm@...ux-foundation.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 7/9 updated] vfs: protect remounting superblock read-only
On Sat, Oct 23, 2010 at 09:35:16PM +0200, Miklos Szeredi wrote:
> > Another thing:
> > "If clone_mnt() happens while mnt_make_readonly() is running, the
> > cloned mount might have MNT_WRITE_HOLD flag set, which results in
> > mnt_want_write() spinning forever on this mount."
> > actually means
> > "neither clone_mnt() nor remounts should ever be done without
> > namespace_sem held exclusive; if that ever happens, we have a serious
> > bug that can lead to any number of bad things happening".
> >
> > Do you actually see such places? If so, that's what needs fixing.
>
> do_remount() takes s_umount, but not namespace_sem.
Duh... Right, ignore that part; we really don't want to do anything
blocking beyond simple allocations under namespace_sem (e.g. everything
that gets unmounted is collected to be dropped after namespace_sem
is released).
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists