linux-ext4 - Re: [stable] Patch Upstream: ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc

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] [day] [month] [year] [list]

Date:	Wed, 14 Jan 2009 20:16:53 -0800
From:	Greg KH <greg@...ah.com>
To:	Theodore Tso <tytso@....edu>
Cc:	aneesh.kumar@...ux.vnet.ibm.com, sct@...hat.com,
	akpm@...ux-foundation.org, adilger@....com, stable@...nel.org,
	linux-ext4@...r.kernel.org
Subject: Re: [stable] Patch Upstream: ext4: Fix s_dirty_blocks_counter if
	block allocation failed with nodelalloc

On Wed, Jan 14, 2009 at 08:30:12PM -0500, Theodore Tso wrote:
> On Wed, Jan 14, 2009 at 03:47:48PM -0800, Greg KH wrote:
> > Hi Ted and others,
> > 
> > I see a bunch of ext4 / jbd2 patches were tagged as requested to go into
> > the -stable tree.  But there seems to not be any simple way to determine
> > what order these patches should go in.
> > 
> > Can someone please list the order of them, or resend all patches that
> > they request to go into the 2.6.28-stable tree (and 2.6.27 if some of
> > the patches apply there as well.)
> 
> I'll put together git branches versus the 2.6.28-stable and
> 2.6.27-stable, hopefully in the next week or so.

Thanks, I'll go drop all ext4 and jbd2 patches from our stable
"to-apply" queue then.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html