linux-kernel - Re: [vfs:fsfreeze] umount BUG: sleeping function called from invalid context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120731085815.GF6481@ZenIV.linux.org.uk>
Date:	Tue, 31 Jul 2012 09:58:15 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Fengguang Wu <fengguang.wu@...el.com>
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 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).
--
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/