linux-kernel - Re: [tree] latest kill-the-BKL tree, v12

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: <63a49ef40904160735w3eab9ea7s3fc5da177ee2ac87@mail.gmail.com>
Date:	Thu, 16 Apr 2009 16:35:58 +0200
From:	Alessio Igor Bogani <abogani@...ware.it>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Alexander Beregalov <a.beregalov@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-nfs@...r.kernel.org, netdev@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Jeff Mahoney <jeffm@...e.com>,
	ReiserFS Development List <reiserfs-devel@...r.kernel.org>,
	Chris Mason <chris.mason@...cle.com>
Subject: Re: [tree] latest kill-the-BKL tree, v12

Dear Sir Molnar,

2009/4/16 Ingo Molnar <mingo@...e.hu>:
[...]
>> This is still the dependency between bkl and s_umount_key that has
>> been reported recently. I wonder if this is not a problem in the
>> fs layer. I should investigate on it.
>
> The problem seem to be that this NFS call context:
>
> -> #0 (kernel_mutex){+.+.+.}:
>       [<00000000004776d0>] lock_acquire+0x5c/0x74
>       [<00000000006f0ebc>] mutex_lock_nested+0x48/0x380
>       [<00000000006f32dc>] lock_kernel+0x28/0x3c
>       [<00000000006d20ec>] rpc_wait_bit_killable+0x64/0x8c
>       [<00000000006f0620>] __wait_on_bit+0x64/0xc0
>       [<00000000006f06e4>] out_of_line_wait_on_bit+0x68/0x7c
>       [<00000000006d2938>] __rpc_execute+0x150/0x2b4
>       [<00000000006d2ac0>] rpc_execute+0x24/0x34
>       [<00000000006cc338>] rpc_run_task+0x64/0x74
>       [<00000000006cc474>] rpc_call_sync+0x58/0x7c
>       [<00000000005717b0>] nfs3_rpc_wrapper+0x24/0xa0
>       [<0000000000572024>] do_proc_get_root+0x6c/0x10c
>       [<00000000005720dc>] nfs3_proc_get_root+0x18/0x5c
>       [<000000000056401c>] nfs_get_root+0x34/0x17c
>       [<0000000000568adc>] nfs_get_sb+0x9ec/0xa7c
>       [<00000000004b7ec8>] vfs_kern_mount+0x44/0xa4
>       [<00000000004b7f84>] do_kern_mount+0x30/0xcc
>       [<00000000004cf300>] do_mount+0x7c8/0x80c
>       [<00000000004ed2a4>] compat_sys_mount+0x224/0x274
>       [<0000000000406154>] linux_sparc_syscall32+0x34/0x40

Proposed patch that i just sent
(http://marc.info/?l=linux-kernel&m=123989213917572&w=2) seems fix the
lock dependency.
I don't know if it is the right way to solve the problem in any case
but it works on my laptop, at least.

Ciao,
Alessio
--
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/