mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessio Igor Bogani <abogani@texware.it>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Mahoney <jeffm@suse.com>,
	ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: [tree] latest kill-the-BKL tree, v12
Date: Thu, 16 Apr 2009 16:35:58 +0200	[thread overview]
Message-ID: <63a49ef40904160735w3eab9ea7s3fc5da177ee2ac87@mail.gmail.com> (raw)
In-Reply-To: <20090416085153.GC9813@elte.hu>

Dear Sir Molnar,

2009/4/16 Ingo Molnar <mingo@elte.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

  reply	other threads:[~2009-04-16 14:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  3:34 [PATCH 0/3] kill-the-BKL/reiserfs: reiserfs fixes Frederic Weisbecker
2009-04-14  3:34 ` [PATCH 1/3] kill-the-BKL/reiserfs: provide a tool to lock only once the write lock Frederic Weisbecker
2009-04-14  3:34 ` [PATCH 2/3] kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file Frederic Weisbecker
2009-04-14  3:34 ` [PATCH 3/3] kill-the-BKL/reiserfs: only acquire the write lock once in reiserfs_dirty_inode Frederic Weisbecker
2009-04-14  4:51 ` [PATCH 0/3] kill-the-BKL/reiserfs: reiserfs fixes Alexander Beregalov
2009-04-14  9:01   ` [tree] latest kill-the-BKL tree, v12 Ingo Molnar
2009-04-14 10:02     ` Edward Shishkin
2009-04-14 21:32       ` Frederic Weisbecker
2009-04-14 21:27     ` Frederic Weisbecker
2009-04-15 22:58     ` Alexander Beregalov
2009-04-15 23:07       ` Ingo Molnar
2009-04-15 23:13         ` Trond Myklebust
2009-04-15 23:35         ` Frederic Weisbecker
2009-04-16  8:51           ` Ingo Molnar
2009-04-16 14:35             ` Alessio Igor Bogani [this message]
2009-04-16 16:40             ` Frederic Weisbecker
2009-04-14 10:00 ` [PATCH 0/3] kill-the-BKL/reiserfs: reiserfs fixes Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63a49ef40904160735w3eab9ea7s3fc5da177ee2ac87@mail.gmail.com \
    --to=abogani@texware.it \
    --cc=a.beregalov@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=chris.mason@oracle.com \
    --cc=fweisbec@gmail.com \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome