Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@profitbricks.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	stable <stable@vger.kernel.org>, Jiri Slaby <jslaby@suse.cz>,
	Sebastian Parschauer <s.parschauer@gmx.de>,
	Yun Wang <yun.wang@profitbricks.com>,
	Gi-Oh Kim <gi-oh.kim@profitbricks.com>
Subject: Re: SCSI fix (a621bac3)missing in stable
Date: Tue, 14 Jun 2016 13:03:14 -0700	[thread overview]
Message-ID: <20160614200314.GA3267@kroah.com> (raw)
In-Reply-To: <CAMGffE=Hx-t_kj7rajkd1OmpD1NH2n-vJ2bOyovgr9UUU-oEJQ@mail.gmail.com>

On Wed, Jun 08, 2016 at 06:47:40PM +0200, Jinpu Wang wrote:
> Hi all,
> 
> We found the SCSI fix is missing in any stable only in linux 4.7-rc2
> [PATCH] scsi_lib: correctly retry failed zero length REQ_TYPE_FS
>  commands
> 
> commit a621bac3044ed6f7ec5fa0326491b2d4838bfa93 upstream.
> 
> So we backport & tested on linux-3.12 (as we're using this kernel).
> Could you review if we did it right?

This "backport" includes a bunch of checks and comments that are not in
the upstream kernel, so I don't really want to include it in the
3.14-stable queue unless you get the scsi maintainers to ack it.

thanks,

greg k-h

  parent reply	other threads:[~2016-06-14 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 16:47 SCSI fix (a621bac3)missing in stable Jinpu Wang
2016-06-08 17:11 ` Greg KH
2016-06-09  8:15   ` Jinpu Wang
2016-06-14 20:03 ` Greg KH [this message]
2016-06-15  8:04   ` Jinpu Wang
2016-06-17 15:29     ` Jinpu Wang
2016-06-17 15:51       ` James Bottomley
2016-06-20 10:23         ` Jinpu Wang
2016-06-21 14:45           ` James Bottomley
2016-06-21 15:31             ` Jinpu Wang
2016-06-29 12:36               ` Jinpu Wang
2016-06-29 16:41                 ` Greg KH
2016-07-12  9:40               ` Jiri Slaby

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=20160614200314.GA3267@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=gi-oh.kim@profitbricks.com \
    --cc=hch@infradead.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jinpu.wang@profitbricks.com \
    --cc=jslaby@suse.cz \
    --cc=martin.petersen@oracle.com \
    --cc=s.parschauer@gmx.de \
    --cc=stable@vger.kernel.org \
    --cc=yun.wang@profitbricks.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