From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [Bug #12610] sync-Regression in 2.6.28.2? Date: Sat, 21 Feb 2009 12:56:46 -0500 Message-ID: <20090221175646.GB3750@mit.edu> References: Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Federico Cuello , Ralf Hildebrandt , bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org 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 > 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