linux-kernel - Re: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:20

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 for Android: free password hash cracker in your pocket

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

Message-ID: <52A717E2.6040907@suse.cz>
Date:	Tue, 10 Dec 2013 14:32:18 +0100
From:	Vlastimil Babka <vbabka@...e.cz>
To:	Tejun Heo <tj@...nel.org>,
	Yuanhan Liu <yuanhan.liu@...ux.intel.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:20

On 12/05/2013 11:50 PM, Tejun Heo wrote:
> On Thu, Dec 05, 2013 at 11:10:51AM +0800, Yuanhan Liu wrote:
>> Greetings,
>>
>> I got the below dmesg and the first bad commit is
>>
>> commit 4b93dc9b1c684d0587fe44d36bbfdf45bd3bea9d
>> Author:     Tejun Heo <tj@...nel.org>
>> AuthorDate: Thu Nov 28 14:54:43 2013 -0500
>> Commit:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> CommitDate: Fri Nov 29 18:16:08 2013 -0800
>>
>>      sysfs, kernfs: prepare mount path for kernfs
>
> Oops, can you please try the following patch?
>
> Thanks.
>
> diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c
> index e7e3aa8..8d07527 100644
> --- a/fs/sysfs/mount.c
> +++ b/fs/sysfs/mount.c
> @@ -45,8 +45,10 @@ static struct dentry *sysfs_mount(struct file_system_type *fs_type,
>
>   static void sysfs_kill_sb(struct super_block *sb)
>   {
> +	void *ns = (void *)kernfs_super_ns(sb);
> +
>   	kernfs_kill_sb(sb);
> -	kobj_ns_drop(KOBJ_NS_TYPE_NET, (void *)kernfs_super_ns(sb));
> +	kobj_ns_drop(KOBJ_NS_TYPE_NET, ns);
>   }
>
>   static struct file_system_type sysfs_fs_type = {

I've had the same problem with linux-next-20131209 and this patch fixed 
it. Feel free to add if appropriate:

Tested-by: Vlastimil Babka <vbabka@...e.cz>

> --
> 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/
>

--
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/