From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org, viro@ftp.linux.org.uk
Subject: Re: [patch, lock validator] fix proc_inum_lock related deadlock
Date: Thu, 26 Jan 2006 01:11:41 +0100 [thread overview]
Message-ID: <20060126001141.GA18181@elte.hu> (raw)
In-Reply-To: <20060126000200.GA12809@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> there's another VFS lock that just popped up, hopefully the last one.
> Fix below. (All this is still related to proc_subdir_lock, and the
> original BKL bug it fixed.)
bah. proc_num_idr.lock nests too ...
i guess we should stick this into free_irq():
WARN_ON(in_interrupt());
and be done with it. If all such places are fixed then Steve's fix
becomes complete.
Ingo
prev parent reply other threads:[~2006-01-26 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 17:03 [patch, validator] fix proc_subdir_lock related deadlock Ingo Molnar
2006-01-25 17:14 ` Steven Rostedt
2006-01-25 18:08 ` Ingo Molnar
2006-01-25 18:14 ` [patch, validator] fix files_lock " Ingo Molnar
2006-01-25 18:23 ` [patch, validator] fix proc_subdir_lock " Andrew Morton
2006-01-25 20:21 ` Ingo Molnar
2006-01-26 0:02 ` [patch, lock validator] fix proc_inum_lock " Ingo Molnar
2006-01-26 0:11 ` Ingo Molnar [this message]
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=20060126001141.GA18181@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=viro@ftp.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).