From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: torvalds@linux-foundation.org,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.27-rc5] inotify_read's ev_mutex vs do_page_fault's mmap_sem...
Date: Wed, 10 Sep 2008 21:10:42 +0100 [thread overview]
Message-ID: <6278d2220809101310l1c6e4810q2d5c56ca693a2d43@mail.gmail.com> (raw)
In-Reply-To: <200809110612.51736.nickpiggin@yahoo.com.au>
On Wed, Sep 10, 2008 at 9:12 PM, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> On Wednesday 10 September 2008 14:07, Nick Piggin wrote:
>> On Wednesday 10 September 2008 07:03, Daniel J Blueman wrote:
>> > I observed this locking violation [1] while gnome-panel was loading;
>> > this was previously reported at
>> > http://uwsg.iu.edu/hypermail/linux/kernel/0806.3/2881.html .
>> >
>> > Let me know for more information/config/testing. Thanks!
>>
>> Thanks for the report. I've attached a patch you could test. It compiles
>> (and boots a UML here) but I don't think I've actually tested the inotify
>> path at all, so it may explode on you.
>
> Indeed it was wrong, I messed up the waitqueue handling. This one
> survives longer for me...
So far, so good with that last patch. I'll continue testing this and
follow up if I find any problem.
Thanks for the patching, Nick!
Daniel
--
Daniel J Blueman
prev parent reply other threads:[~2008-09-10 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 21:03 Daniel J Blueman
2008-09-10 4:07 ` Nick Piggin
2008-09-10 7:57 ` Peter Zijlstra
2008-09-10 8:03 ` Nick Piggin
2008-09-10 8:37 ` Ingo Molnar
2008-09-10 9:50 ` Nick Piggin
2008-09-10 9:59 ` Peter Zijlstra
2008-09-10 20:11 ` Nick Piggin
2008-09-10 20:12 ` Nick Piggin
2008-09-10 20:10 ` Daniel J Blueman [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=6278d2220809101310l1c6e4810q2d5c56ca693a2d43@mail.gmail.com \
--to=daniel.blueman@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®