linux-kernel - Re: version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas

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]

Message-ID: <20161213205129.w5xzwwuwy5llqywc@sasha-lappy>
Date:   Tue, 13 Dec 2016 20:51:31 +0000
From:   alexander.levin@...izon.com
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     James Bottomley <James.Bottomley@...senPartnership.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        Dashi DS1 Cao <caods1@...ovo.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-scsi <linux-scsi@...r.kernel.org>,
        stable <stable@...r.kernel.org>
Subject: Re: version 3.18.44 to 3.18.45 introduced a bug in
 "drivers/scsi/megaraid/megaraid_sas_base.c"

On Tue, Dec 13, 2016 at 08:47:33AM -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 13, 2016 at 08:43:41AM -0800, James Bottomley wrote:
> > On Tue, 2016-12-13 at 08:33 -0800, Randy Dunlap wrote:
> > > On 12/13/16 08:30, Greg Kroah-Hartman wrote:
> > > > I don't maintain 3.18-stable :)
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > > 
> > > 
> > > Thanks. My bad.
> > > 
> > > adding Sasha.
> > 
> > This was all covered here:
> > 
> > https://www.spinics.net/lists/stable/msg150608.html
> > 
> > How did it get missed, and what should the process be?
> 
> I don't know how that got missed, did the "fixup" patch never make it
> into 3.18-stable?  I know Sasha has been slow on that kernel, and it's
> about to go end-of-life, so perhaps he's just releasing them on a slower
> cycle at the moment...

I think that what happened there is that I built the branch before the fixup
was upstreamed, so I never noticed that.

It's queued up right now, but I don't think I'll make another release except
a final one in January when it EOLs.

If this fix is urgent for anyone then something is wrong as this kernel dies
in two weeks...

-- 

Thanks,
Sasha