[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120731091326.GA15095@localhost>
Date: Tue, 31 Jul 2012 17:13:26 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [vfs:fsfreeze] umount BUG: sleeping function called from invalid
context
On Tue, Jul 31, 2012 at 09:58:15AM +0100, Al Viro wrote:
> On Tue, Jul 31, 2012 at 04:38:39PM +0800, Fengguang Wu wrote:
> > Hi Jan,
> >
> > Here is another warning for the fs freeze series.
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fsfreeze
> > head: 7aff72a61f45337d83ab2b7fb16d7b542db16ad8
> > commit: bc875c078f72993e6c44925cdedef5a304ca7429 [37/51] fs: Improve filesystem freezing handling
> >
> > The warning shows up reliably since commit bc875c0. The 2nd commit
> > 51205f9 triggers the same warning as the previous email.
>
> That one is fixed in the end of #fsfreeze (for testing purposes only) and then the right
> way in #for-next (by making percpu_list_lock a spinlock).
Ah sorry. It seems that you quickly pushed the fix
commit c91dc212879946b8e542773394cb56e6e3c6e1ae
CommitDate: Tue Jul 31 01:57:53 2012 +0400
[ewww][testing-only] deal with b0rken use of percpu_counter_destroy() under spinlock
while I'm still testing the slightly old head:
commit 7aff72a61f45337d83ab2b7fb16d7b542db16ad8
CommitDate: Tue Jul 31 01:21:32 2012 +0400
Documentation: Correct s_umount state for freeze_fs/unfreeze_fs
Thanks,
Fengguang
--
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