linux-kernel - Re: ext4 locks under 2.6.28.3..6

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: <20090222011617.GD17066@mit.edu>
Date:	Sat, 21 Feb 2009 20:16:17 -0500
From:	Theodore Tso <tytso@....edu>
To:	Luciano Miguel Ferreira Rocha <luciano@...otux.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ext4 locks under 2.6.28.3..6

On Fri, Feb 20, 2009 at 10:34:43AM +0000, Luciano Miguel Ferreira Rocha wrote:
> 
> I've experienced intermittent locks on my ext4 filesystems under kernel
> 2.6.28.3 till 2.6.28.6.

Are you still seeing the problem now that you're using 2.6.28.6?  It
looks to me to be another case of bug

http://bugzilla.kernel.org/show_bug.cgi?id=12579
http://bugzilla.kernel.org/show_bug.cgi?id=12610

As I commented in bugid 12610:

>This fix for this has landed in mainline post 2.6.29-rc5, as commit
>2acf2c.  The deadlock is technically not a regression but it was made
>*much* more likely to show up because of commit 31a1266: ("mm:
>write_cache_pages cyclic fix, which show up in 2.6.28.1").
>
>Commit 3a4c68 in mainline backs up the change made in 31a1266, so you
>probably won't see this much after 2.6.28.6 (when 3a4c68 was
>backported to 2.6.28.y), but we should get commit 2acf2c pushed to
>2.6.28.x and 2.6.27.y to completely solve the deadlock problem.

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