linux-kernel - Re: XFS deadlock in 2.6.37

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: <20110120112730.393f6ff0@petrie>
Date:	Thu, 20 Jan 2011 11:27:30 -0600
From:	William Pitcock <nenolod@...eferenced.org>
To:	Malcolm Scott <lkml@...c.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: XFS deadlock in 2.6.37

Hi,

On Thu, 20 Jan 2011 17:08:45 +0000 (GMT)
Malcolm Scott <lkml@...c.org.uk> wrote:

> Hi all,
> 
> I've had the following deadlock happen twice on a 2.6.37 system with
> several XFS filesystems (including root) and no swap (may be
> relevant, considering that kswapd is one task involved here).  Some
> minor filesystem corruption resulted (but maybe only because the root
> fs couldn't be synced/umounted).
> 

kswapd also handles swapping pages in and out of the filesystem cache
as part of the VM subsystem.  I have a hunch that if you do a bisect
of commits relating to the VM subsystem, you will find the commit that
is causing this.

Also, are you building with BKL enabled or disabled?

William
--
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/