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: <20120816164735.6a0cdef0@notabene.brown>
Date:	Thu, 16 Aug 2012 16:47:35 +1000
From:	NeilBrown <neilb@...e.de>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [v2.6.34-stable 035/165] md: Fix handling for devices from 2TB
 to 4TB in 0.90 metadata.

On Thu, 16 Aug 2012 05:24:33 +0100 Ben Hutchings <ben@...adent.org.uk> wrote:

> On Thu, 2012-08-16 at 06:46 +1000, NeilBrown wrote:
> > On Wed, 15 Aug 2012 15:46:19 -0400 Paul Gortmaker
> > <paul.gortmaker@...driver.com> wrote:
> > 
> > > From: NeilBrown <neilb@...e.de>
> > > 
> > >                    -------------------
> > >     This is a commit scheduled for the next v2.6.34 longterm release.
> > >     http://git.kernel.org/?p=linux/kernel/git/paulg/longterm-queue-2.6.34.git
> > >     If you see a problem with using this for longterm, please comment.
> > 
> > This patch fixes one problem but unfortunately introduces another.
> > The patch for that 'other' should get sent to linus in the next day or so
> > after it has had a chance to sit in -next for a bit.
> > 
> > It can be found at:
> >  http://neil.brown.name/git?p=md;a=commitdiff;h=30b798a352052b07c924956dda4ce720b00af711
> > 
> > you could either add that patch, or drop this patch until the next cycle.
> [...]
> 
> This was already backported to 2.6.32, 2.6.33 and 3.0.  So please change
> the last sentence of the commit message for your following fix; it will
> be needed for all active stable series.
>

I had been wondering about that.  You've convinced me.  It now reads:

    This bug was introduced in 3.1 and is suitable for any stable kernels
    from then onwards.
    As the offending commit was tagged for 'stable', any stable kernel
    that it was applied to should also get this patch.  That includes
    at least 2.6.32, 2.6.33 and 3.0. (Thanks to Ben Hutchings for
    providing that list).

Thanks,
NeilBrown


Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ