[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090221175646.GB3750@mit.edu>
Date: Sat, 21 Feb 2009 12:56:46 -0500
From: Theodore Tso <tytso@....edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Federico Cuello <fedux@...men.org.ar>,
Ralf Hildebrandt <Ralf.Hildebrandt@...rite.de>,
bugme-daemon@...zilla.kernel.org
Subject: Re: [Bug #12610] sync-Regression in 2.6.28.2?
On Sat, Feb 14, 2009 at 09:38:18PM +0100, Rafael J. Wysocki wrote:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12610
> Subject : sync-Regression in 2.6.28.2?
> Submitter : Ralf Hildebrandt <Ralf.Hildebrandt@...rite.de>
> Date : 2009-01-27 9:35 (19 days old)
> References : http://marc.info/?l=linux-kernel&m=123304977706620&w=4
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/
Powered by blists - more mailing lists