From: Oliver Neukum <oneukum@suse.com>
To: Tom Yan <tom.ty89@gmail.com>
Cc: David Lang <david@lang.hm>,
james harvey <jamespharvey20@gmail.com>,
Tejun Heo <tj@kernel.org>,
regressions@leemhuis.info, gregkh@linuxfoundation.org,
hdegoede@redhat.com, Alan Stern <stern@rowland.harvard.edu>,
Pavel Machek <pavel@ucw.cz>,
linux-ide@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Date: Sun, 14 Aug 2016 16:14:59 +0200 [thread overview]
Message-ID: <1471184099.4879.3.camel@suse.com> (raw)
In-Reply-To: <CAGnHSEnwQ-sTMnKaZBGD-n2vu83B5nnWTugO9+44oq7dnVOztw@mail.gmail.com>
On Sun, 2016-08-14 at 10:53 +0000, Tom Yan wrote:
> Btw, why hasn't this been CC'd to linux-scsi at the very least? The
> SCSI disk (sd) driver is obviously the sociopath here. It should
> really differentiate disks from libata and usb-storage/uas, and wait
> for at least a minute to see if there's gonna be an ATA drive popping
> up before enumerating disks from the latter. Sociopaths like me that
> put the root filesystem on an UAS drive should really be ignored.
> Wait, there's NVMe! Problem solved.
We most certainly cannot introduce such a delay. If this really
must be done, we need synchronisation primitives between the
subsystemes, or we need stable names in kernel space.
Regards
Oliver
next prev parent reply other threads:[~2016-08-14 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160813190340.GA29989@amd>
2016-08-14 9:20 ` Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek
2016-08-14 9:34 ` Tom Yan
2016-08-14 10:01 ` Pavel Machek
2016-08-14 10:07 ` Tom Yan
2016-08-14 10:17 ` Tom Yan
2016-08-14 10:26 ` David Lang
2016-08-14 10:53 ` Tom Yan
2016-08-14 14:14 ` Oliver Neukum [this message]
[not found] ` <alpine.DEB.2.02.1608140322400.9045-UEhY+ZBZOcqqLGM74eQ/YA@public.gmane.org>
2016-08-14 11:29 ` Greg KH
2016-08-14 12:03 ` Pavel Machek
2016-08-14 14:15 ` Greg KH
2016-08-14 14:56 ` Alan Stern
2016-08-14 16:13 ` Pavel Machek
2016-08-14 11:10 ` Pavel Machek
2016-08-14 11:41 ` Tom Yan
2016-08-14 16:09 ` One Thousand Gnomes
2016-08-14 10:14 ` Pavel Machek
2016-08-14 16:06 ` Pavel Machek
2016-08-14 17:55 ` Pavel Machek
2016-08-14 18:22 ` Hans de Goede
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=1471184099.4879.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=david@lang.hm \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jamespharvey20@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=regressions@leemhuis.info \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=tom.ty89@gmail.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