Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1541521

Re: version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas_base.c"

Path csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From alexander.levin@verizon.com
Newsgroups linux.kernel
Subject Re: version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas_base.c"
Date Tue, 13 Dec 2016 22:00:02 +0100
Message-ID <sO2l4-5Po-11@gated-at.bofh.it> (permalink)
References <sNSYq-aO-45@gated-at.bofh.it> <sNXOp-3i2-17@gated-at.bofh.it> <sNYhr-3rV-17@gated-at.bofh.it> <sNYhr-3rV-35@gated-at.bofh.it> <sNYr7-3vi-11@gated-at.bofh.it> <sNYr7-3vi-17@gated-at.bofh.it>
X-Original-To Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1481662395; x=1513198395; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2SZoD9qRMnocY9yRrvILvswjlfa1tdHj9ZCgIaIsfqA=; b=dtoCxTieWWykVSkZF6G3qDregIohviwcodTH6eXsE23aN6iip0tNNQGs eeIgvEReodCEVawHEjdQPRyCdBtd7iBi+e4DoXvN4cC+qaP+d6+nn8rbF yWiLEjVvT5hmrc0/fFNERUakM2qoDCZ7Rdr7jjnlSHPoMiw3PJozmowPB Q=;
X-Ironport-Anti-Spam-Filtered false
X-Ironport-Av E=Sophos;i="5.33,342,1477958400"; d="scan'208";a="1335584864"
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1481662299; x=1513198299; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2SZoD9qRMnocY9yRrvILvswjlfa1tdHj9ZCgIaIsfqA=; b=aT7bVZUG+T/P1vHy+a2REZGgm7NlD7cRAkMhzeCJXDc5z0XjvAbKaRPb /QRPuGRBBcPvfMzmoQgdYQ2PCxzMExd6V0ZzKkpMNw/7Te8HvKVWUV2qW vW88yQ9+TJi4FUjw6kxyuOyRNpUhfxIRD5K2ONfOdg6q/PA/jhwi61Yby I=;
X-Host discovery.odc.vzwcorp.com
Thread-Topic version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas_base.c"
Thread-Index AQHSVYKvWV1E6ilW6U2ZEdeJJSl66g==
Accept-Language en-US
Content-Language en-US
User-Agent Mutt/1.6.2-neo (2016-08-21)
X-Ms-Exchange-Messagesentrepresentingtype 1
X-Ms-Exchange-Transport-Fromentityheader Hosted
X-Originating-IP [10.144.60.250]
Content-Type text/plain; charset="us-ascii"
Content-ID <81219054FB6F3C40A308D23C855D02C6@vzwcorp.com>
Content-Transfer-Encoding quoted-printable
MIME-Version 1.0
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 42
Organization linux.* mail to news gateway
X-Original-Cc James Bottomley <James.Bottomley@HansenPartnership.com>, Randy Dunlap <rdunlap@infradead.org>, Dashi DS1 Cao <caods1@lenovo.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, linux-scsi <linux-scsi@vger.kernel.org>, stable <stable@vger.kernel.org>
X-Original-Date Tue, 13 Dec 2016 20:51:31 +0000
X-Original-Message-ID <20161213205129.w5xzwwuwy5llqywc@sasha-lappy>
X-Original-References <23B7B563BA4E9446B962B142C86EF24ADB6F24@CNMAILEX03.lenovo.com> <a9788b9c-6361-f79e-f851-e8c4871571cb@infradead.org> <20161213163013.GB20693@kroah.com> <f08db306-7e67-ff4d-979d-8baa82c40671@infradead.org> <1481647421.2473.36.camel@HansenPartnership.com> <20161213164733.GA21910@kroah.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1541521

Show key headers only | View raw


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

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" Dashi DS1 Cao <caods1@lenovo.com> - 2016-12-13 12:00 +0100
  Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" Randy Dunlap <rdunlap@infradead.org> - 2016-12-13 17:10 +0100
    Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-12-13 17:40 +0100
      Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" Randy Dunlap <rdunlap@infradead.org> - 2016-12-13 17:40 +0100
        Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-12-13 17:50 +0100
          Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" alexander.levin@verizon.com - 2016-12-13 22:00 +0100
        Re: version 3.18.44 to 3.18.45 introduced a bug in  "drivers/scsi/megaraid/megaraid_sas_base.c" James Bottomley <James.Bottomley@HansenPartnership.com> - 2016-12-13 17:50 +0100

csiph-web