From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: longli@microsoft.com
Cc: KY Srinivasan <kys@microsoft.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
sthemmin@microsoft.com,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
devel@linuxdriverproject.org,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors
Date: Mon, 27 Mar 2017 16:22:09 -0400 [thread overview]
Message-ID: <5df6cd65-92d5-e4c5-56e3-771643f86861@canonical.com> (raw)
Hi Long Li,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 40630f462824ee24bc00d692865c86c3828094e0
Author: Long Li <longli@microsoft.com>
Date: Wed Dec 14 18:46:03 2016 -0800
scsi: storvsc: properly set residual data length on errors
The regression was introduced in mainline as of v4.11-rc1. It was also
cc'd to stable and has landed in v3.12.y, v4.4.y, v4.9.y and v4.10.y.
This regression seems pretty severe since it's preventing virtual
machines from booting. It's affecting a couple of users so far. I was
hoping to get your feedback, since you are the patch author. Do you
think gathering any additional data will help diagnose this issue, or
would it be best to submit a revert request?
Thanks,
Joe
[0] http://pad.lv/1674635
next reply other threads:[~2017-03-27 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 20:22 Joseph Salisbury [this message]
2017-03-27 22:14 ` [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors Stephen Hemminger
2017-03-27 22:25 ` Joseph Salisbury
2017-03-28 14:28 ` Joseph Salisbury
2017-03-28 16:14 ` Stephen Hemminger
2017-03-30 8:03 ` Greg KH
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=5df6cd65-92d5-e4c5-56e3-771643f86861@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.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).