From: Alex Williamson <alex.williamson@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Sagi Grimberg <sagig@mellanox.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 3.15 099/139] libiscsi, iser: Adjust data_length to include protection information
Date: Wed, 02 Jul 2014 17:19:35 -0600 [thread overview]
Message-ID: <1404343175.1862.74.camel@ul30vt.home> (raw)
In-Reply-To: <1404341555.16066.19.camel@dabdike>
On Wed, 2014-07-02 at 15:52 -0700, James Bottomley wrote:
> On Wed, 2014-07-02 at 17:44 -0500, Mike Christie wrote:
> > On 07/02/2014 05:15 PM, Alex Williamson wrote:
> > > On Sat, 2014-06-28 at 10:47 -0700, Greg Kroah-Hartman wrote:
> > >> > 3.15-stable review patch. If anyone has any objections, please let me know.
> > >> >
> > >> > ------------------
> > >> >
> > >> > From: Sagi Grimberg <sagig@mellanox.com>
> > >> >
> > >> > commit d77e65350f2d82dfa0557707d505711f5a43c8fd upstream.
> > >> >
> > >> > In case protection information exists over the wire
> > >> > iscsi header data length is required to include it.
> > >> > Use protection information aware scsi helpers to set
> > >> > the correct transfer length.
> > >> >
> > >> > In order to avoid breakage, remove iser transfer length
> > >> > checks for each task as they are not always true and
> > >> > somewhat redundant anyway.
> > >> >
> > >> > Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
> > >> > Reviewed-by: Mike Christie <michaelc@cs.wisc.edu>
> > >> > Acked-by: Mike Christie <michaelc@cs.wisc.edu>
> > >> > Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
> > >> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > >> >
> > >> > ---
> > >> > drivers/infiniband/ulp/iser/iser_initiator.c | 34 +++++++--------------------
> > >> > drivers/scsi/libiscsi.c | 18 +++++++-------
> > >> > 2 files changed, 19 insertions(+), 33 deletions(-)
> > > I'm a bit late to object, but this is causing a regression for me on
> > > 3.15.3 and 3.16-rc. Using an iscsi_tcp rootfs, I'm seeing the NULL
> >
> >
> > A fix for this is in Christoph's tree. Here is the status of the patch.
> >
> > http://marc.info/?l=linux-kernel&m=140432482527273&w=2
>
> I assume it's this fix:
>
> commit 7bafc240e126c37f60b040fa429ae4a710b88ab5
> Author: Martin K. Petersen <martin.petersen@oracle.com>
> Date: Tue Jun 24 16:59:35 2014 +0200
>
> scsi: use the scsi data buffer length to extract transfer size
>
> In which case it's not marked for stable backport ... I assume it should
> be?
Yes, that's the one. It definitely needs a 3.15 stable backport.
Thanks,
Alex
next prev parent reply other threads:[~2014-07-02 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140628174605.352098823@linuxfoundation.org>
[not found] ` <20140628174609.930049472@linuxfoundation.org>
[not found] ` <1404339330.1862.69.camel@ul30vt.home>
2014-07-02 22:44 ` [PATCH 3.15 099/139] libiscsi, iser: Adjust data_length to include protection information Mike Christie
2014-07-02 22:48 ` Alex Williamson
2014-07-03 6:05 ` Christoph Hellwig
2014-07-02 22:52 ` James Bottomley
2014-07-02 23:19 ` Alex Williamson [this message]
2014-07-03 0:05 ` Nicholas A. Bellinger
2014-07-03 6:05 ` Christoph Hellwig
2014-07-03 13:54 ` James Bottomley
2014-07-03 16:27 ` Greg Kroah-Hartman
2014-07-03 16:33 ` Christoph Hellwig
2014-07-03 18:00 ` James Bottomley
2014-07-06 12:27 ` Sagi Grimberg
2014-07-03 16:28 ` Christoph Hellwig
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=1404343175.1862.74.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=sagig@mellanox.com \
--cc=stable@vger.kernel.org \
/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