linux-kernel - Re: XFS deadlock fixed?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110511153501.GA8457@infradead.org>
Date:	Wed, 11 May 2011 11:35:01 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Felipe Wilhelms Damasio - Taghos <felipewd@...hos.com.br>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: XFS deadlock fixed?

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/