From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Alex Williamson <alex.williamson@redhat.com>,
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: Thu, 03 Jul 2014 06:54:05 -0700 [thread overview]
Message-ID: <1404395645.1949.2.camel@jarvis.lan> (raw)
In-Reply-To: <20140703060548.GB17456@infradead.org>
On Wed, 2014-07-02 at 23:05 -0700, Christoph Hellwig wrote:
> On Wed, Jul 02, 2014 at 03:52:35PM -0700, James Bottomley wrote:
> > In which case it's not marked for stable backport ... I assume it should
> > be?
>
> Only if the patch that regression went to stable, which it shouldn't,
Well it did:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/scsi?h=linux-3.15.y&id=04423ddea30a7fb7232636eda8aed55ea5b972fe
The stable process is a bit broken from my point of view since it
doesn't copy linux-scsi on SCSI commits ... but this time even I didn't
get a cc, so really no-one who knew there was a problem had a chance to
comment.
The choice is either request revert from stable or add fix.
James
next prev parent reply other threads:[~2014-07-03 13:54 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
2014-07-03 0:05 ` Nicholas A. Bellinger
2014-07-03 6:05 ` Christoph Hellwig
2014-07-03 13:54 ` James Bottomley [this message]
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=1404395645.1949.2.camel@jarvis.lan \
--to=james.bottomley@hansenpartnership.com \
--cc=alex.williamson@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.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