From: Greg KH <greg@kroah.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: stable <stable@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: Hyper-V SSD passthrough fix backport
Date: Wed, 29 Nov 2017 09:06:20 +0100 [thread overview]
Message-ID: <20171129080620.GC1918@kroah.com> (raw)
In-Reply-To: <CALjAwxi7=w7AcTC-SfhpHbm=j5n_N5DrkgdZ_o53WhbMHiw+9A@mail.gmail.com>
On Tue, Nov 28, 2017 at 10:58:25PM +0000, Sitsofe Wheeler wrote:
> I'd like to nominate f1c635b439a5c01776fe3a25b1e2dc546ea82e6f
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?id=f1c635b439a5c01776fe3a25b1e2dc546ea82e6f
> ) to be backported to 4.4 stable because it looks like without it
> passthrough SSD disks won't work and will generate faux devices. It is
> also being carried by Ubuntu:
> http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/log/drivers/scsi/storvsc_drv.c?h=Ubuntu-4.4.0-98.121
> along with other Hyper-V patches in their 4.4 tree.
>
> I'm not 100% sure that this one will fix what is being seen but I'm
> coming to this conclusion based on
> https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1679898/comments/144
Can you test it to determine if this really does what you think it does
to solve the problem? The changelog text makes it seem not necessary at
all.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-29 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 22:58 Hyper-V SSD passthrough fix backport Sitsofe Wheeler
2017-11-29 8:06 ` Greg KH [this message]
2017-11-29 8:11 ` Sitsofe Wheeler
2017-11-29 10:40 ` Sitsofe Wheeler
2017-11-29 12:09 ` Sitsofe Wheeler
2017-11-29 23:21 ` Stephen Hemminger
2017-12-04 12:10 ` Greg KH
2017-12-07 7:10 ` Sitsofe Wheeler
2017-12-07 14:17 ` Haiyang Zhang
2017-12-08 18:12 ` Stephen Hemminger
2017-12-12 8:26 ` 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=20171129080620.GC1918@kroah.com \
--to=greg@kroah.com \
--cc=martin.petersen@oracle.com \
--cc=sitsofe@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).