linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Tom Yan <tom.ty89@gmail.com>,
	linux-scsi@vger.kernel.org, damien.lemoal@wdc.com,
	martin.petersen@oracle.com, sashal@kernel.org,
	stable@vger.kernel.org
Subject: Re: [Regression][Stable] sd use scsi_mode_sense with invalid param
Date: Sat, 27 Nov 2021 12:55:42 +0100	[thread overview]
Message-ID: <YaIcvg3LgfCjwxfF@kroah.com> (raw)
In-Reply-To: <92cc74fd-ce93-b844-830f-71e744e0c084@opensource.wdc.com>

On Sat, Nov 27, 2021 at 10:15:51AM +0900, Damien Le Moal wrote:
> On 2021/11/27 6:33, Tom Yan wrote:
> > Hi Greg,
> > 
> > Could you help pulling c749301ebee82eb5e97dec14b6ab31a4aabe37a6 into
> > the stable branches in which 17b49bcbf8351d3dbe57204468ac34f033ed60bc
> > has been pulled? Thanks!
> 
> Yeah, in retrospect, these 2 patches should really have been squashed together.
> Sorry about that. Note that none of these were marked for stable though. I think
> that Sasha's bot picked-up automatically
> 17b49bcbf8351d3dbe57204468ac34f033ed60bc for stable because of the "Fix" in the
> commit title. But c749301ebee82eb5e97dec14b6ab31a4aabe37a6 also has "Fix" in its
> title but was not picked-up. Weird.
> 
> Greg, Martin,
> 
> To fix this, c749301ebee82eb5e97dec14b6ab31a4aabe37a6 is needed in stable !
> 
> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=215137

Now queued up, thanks.

greg k-h

      reply	other threads:[~2021-11-27 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 21:11 [Regression][Stable] sd use scsi_mode_sense with invalid param Tom Yan
2021-11-26 21:21 ` Tom Yan
2021-11-26 21:33   ` Tom Yan
2021-11-27  1:15     ` Damien Le Moal
2021-11-27 11:55       ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YaIcvg3LgfCjwxfF@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=damien.lemoal@wdc.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tom.ty89@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).