From: Peter Zijlstra <peterz@infradead.org>
To: MinChan Kim <minchan.kim@gmail.com>
Cc: Nick Piggin <npiggin@suse.de>,
linux kernel <linux-kernel@vger.kernel.org>,
linux mm <linux-mm@kvack.org>
Subject: Re: [BUG??] Deadlock between kswapd and sys_inotify_add_watch(lockdep report)
Date: Mon, 02 Feb 2009 11:40:02 +0100 [thread overview]
Message-ID: <1233571202.4787.124.camel@laptop> (raw)
In-Reply-To: <28c262360902020225w6419089ft2dda30da9dfb32a9@mail.gmail.com>
On Mon, 2009-02-02 at 19:25 +0900, MinChan Kim wrote:
> But, I am not sure whether it's real bug or not.
Me neither, inode life-times are tricky, but on first sight it looks
real enough.
> I always suffer from reading lockdep report's result. :(
> It would be better to have a document about lockdep report analysis.
I've never found them hard to read, so I'm afraid you'll have to be more
explicit about what is unclear to you.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: MinChan Kim <minchan.kim@gmail.com>
Cc: Nick Piggin <npiggin@suse.de>,
linux kernel <linux-kernel@vger.kernel.org>,
linux mm <linux-mm@kvack.org>
Subject: Re: [BUG??] Deadlock between kswapd and sys_inotify_add_watch(lockdep report)
Date: Mon, 02 Feb 2009 11:40:02 +0100 [thread overview]
Message-ID: <1233571202.4787.124.camel@laptop> (raw)
In-Reply-To: <28c262360902020225w6419089ft2dda30da9dfb32a9@mail.gmail.com>
On Mon, 2009-02-02 at 19:25 +0900, MinChan Kim wrote:
> But, I am not sure whether it's real bug or not.
Me neither, inode life-times are tricky, but on first sight it looks
real enough.
> I always suffer from reading lockdep report's result. :(
> It would be better to have a document about lockdep report analysis.
I've never found them hard to read, so I'm afraid you'll have to be more
explicit about what is unclear to you.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-02 10:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 10:17 [BUG??] Deadlock between kswapd and sys_inotify_add_watch(lockdep report) MinChan Kim
2009-02-02 10:17 ` MinChan Kim
2009-02-02 10:25 ` MinChan Kim
2009-02-02 10:25 ` MinChan Kim
2009-02-02 10:40 ` Peter Zijlstra [this message]
2009-02-02 10:40 ` Peter Zijlstra
2009-02-02 11:27 ` MinChan Kim
2009-02-02 11:27 ` MinChan Kim
2009-02-02 11:44 ` Peter Zijlstra
2009-02-02 11:44 ` Peter Zijlstra
2009-02-02 11:56 ` MinChan Kim
2009-02-02 11:56 ` MinChan Kim
2009-02-02 13:09 ` Peter Zijlstra
2009-02-02 13:09 ` Peter Zijlstra
2009-02-02 13:43 ` MinChan Kim
2009-02-02 13:43 ` MinChan Kim
2009-02-02 13:55 ` Peter Zijlstra
2009-02-02 13:55 ` Peter Zijlstra
2009-02-02 14:16 ` MinChan Kim
2009-02-02 14:16 ` MinChan Kim
2009-02-03 3:03 ` Nick Piggin
2009-02-03 3:03 ` Nick Piggin
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=1233571202.4787.124.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.