From: Christoph Hellwig <hch@infradead.org>
To: Felipe Wilhelms Damasio - Taghos <felipewd@taghos.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS deadlock fixed?
Date: Wed, 11 May 2011 11:35:01 -0400 [thread overview]
Message-ID: <20110511153501.GA8457@infradead.org> (raw)
In-Reply-To: <4DC8B397.20207@taghos.com.br>
On Tue, May 10, 2011 at 12:40:07AM -0300, Felipe Wilhelms Damasio - Taghos wrote:
> Hi Mr. Hellwig,
>
> I saw the XFS deadlock thread regarding 2.6.38:
>
> http://www.linux.sgi.com/archives/xfs/2011-03/msg00185.html
>
> I'm seeing too in 2.6.38.4. A lot of
>
> XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
You're probably running into a different issue. Any chance you can try
the attached patch to see where you're stuck exactly?
Also in case you're using slub (CONFIG_SLUB) can you check if it still
happens when using slab (CONFIG_SLAB) instead?
next prev parent reply other threads:[~2011-05-11 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 3:40 XFS deadlock fixed? Felipe Wilhelms Damasio - Taghos
2011-05-11 15:35 ` Christoph Hellwig [this message]
2011-05-11 15:35 ` 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=20110511153501.GA8457@infradead.org \
--to=hch@infradead.org \
--cc=felipewd@taghos.com.br \
--cc=linux-kernel@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