From: Michel Lespinasse <walken@google.com>
To: Sean Noonan <Sean.Noonan@twosigma.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Martin Bligh <Martin.Bligh@twosigma.com>,
Trammell Hudson <Trammell.Hudson@twosigma.com>,
Christos Zoulas <Christos.Zoulas@twosigma.com>,
"linux-xfs@oss.sgi.com" <linux-xfs@oss.sgi.com>,
Stephen Degler <Stephen.Degler@twosigma.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: XFS memory allocation deadlock in 2.6.38
Date: Mon, 28 Mar 2011 17:25:24 -0700 [thread overview]
Message-ID: <BANLkTikzpC9DdaoWaUTvO98jnjFdJOomwQ@mail.gmail.com> (raw)
In-Reply-To: <081DDE43F61F3D43929A181B477DCA95639B534E@MSXAOA6.twosigma.com>
On Mon, Mar 28, 2011 at 2:34 PM, Sean Noonan <Sean.Noonan@twosigma.com> wrote:
>> Could you test if you see the deadlock before
>> 5ecfda041e4b4bd858d25bbf5a16c2a6c06d7272 without MAP_POPULATE ?
>
> Built and tested 72ddc8f72270758951ccefb7d190f364d20215ab.
> Confirmed that the original bug does not present in this version.
> Confirmed that removing MAP_POPULATE does cause the deadlock to occur.
It seems that the test (without MAP_POPULATE) reveals that the root
cause is an xfs bug, which had been hidden up to now by MAP_POPULATE
preallocating disk blocks (but could always be triggered by the same
test without the MAP_POPULATE flag). I'm not sure how to go about
debugging the xfs deadlock; it would probably be best if an xfs person
could have a look ?
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-29 0:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <081DDE43F61F3D43929A181B477DCA95639B52FD@MSXAOA6.twosigma.com>
[not found] ` <081DDE43F61F3D43929A181B477DCA95639B5327@MSXAOA6.twosigma.com>
2011-03-24 17:43 ` XFS memory allocation deadlock in 2.6.38 Christoph Hellwig
2011-03-24 23:45 ` Michel Lespinasse
2011-03-28 14:58 ` Sean Noonan
2011-03-28 21:06 ` Michel Lespinasse
2011-03-28 21:34 ` Sean Noonan
2011-03-29 0:25 ` Michel Lespinasse [this message]
2011-03-29 1:51 ` Dave Chinner
2011-03-29 2:49 ` Sean Noonan
2011-03-29 19:05 ` Sean Noonan
2011-03-29 19:24 ` 'Christoph Hellwig'
2011-03-29 19:39 ` Johannes Weiner
2011-03-29 19:43 ` 'Christoph Hellwig'
2011-03-29 19:46 ` Sean Noonan
2011-03-29 20:02 ` 'Christoph Hellwig'
2011-03-29 20:23 ` Sean Noonan
2011-03-29 22:42 ` Dave Chinner
2011-03-29 22:45 ` Sean Noonan
2011-03-30 9:23 ` 'Christoph Hellwig'
2011-03-29 19:54 ` Sean Noonan
2011-03-30 0:09 ` Dave Chinner
2011-03-30 1:32 ` Sean Noonan
2011-03-30 1:44 ` Dave Chinner
2011-03-30 1:52 ` Sean Noonan
2011-03-30 9:30 ` 'Christoph Hellwig'
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=BANLkTikzpC9DdaoWaUTvO98jnjFdJOomwQ@mail.gmail.com \
--to=walken@google.com \
--cc=Christos.Zoulas@twosigma.com \
--cc=Martin.Bligh@twosigma.com \
--cc=Sean.Noonan@twosigma.com \
--cc=Stephen.Degler@twosigma.com \
--cc=Trammell.Hudson@twosigma.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@oss.sgi.com \
/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).