linux-kernel - Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGnHSEnwQ-sTMnKaZBGD-n2vu83B5nnWTugO9+44oq7dnVOztw@mail.gmail.com>
Date:	Sun, 14 Aug 2016 10:53:53 +0000
From:	Tom Yan <tom.ty89@...il.com>
To:	David Lang <david@...g.hm>
Cc:	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	james harvey <jamespharvey20@...il.com>,
	regressions@...mhuis.info, hdegoede@...hat.com,
	Tejun Heo <tj@...nel.org>, linux-ide@...r.kernel.org,
	gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
	Oliver Neukum <oliver@...kum.org>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking
 boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

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.

On 14 August 2016 at 10:26, David Lang <david@...g.hm> wrote:
> On Sun, 14 Aug 2016, Tom Yan wrote:
>
>> On 14 August 2016 at 18:07, Tom Yan <tom.ty89@...il.com> wrote:
>>>
>>> On 14 August 2016 at 18:01, Pavel Machek <pavel@....cz> wrote:
>>>>
>>>>
>>>> Since SATA support was merged, certainly since v2.4, and from way
>>>> before /dev/disk/by-id existed.
>>>
>>>
>>> I have no idea how "SATA before USB" had been done in the past (if it
>>> was ever a thing in the kernel), but that has not been the case since
>>> at least v3.0 AFAIR.
>>>
>>>>
>>>> People may not run udev, and you can't use /dev/disk/by-id on kernel
>>>> command line.
>>>>
>>>
>>> No, but you can always use root=PARTUUID=, that's built into the
>>> kernel. (root=UUID= requires udev or so though).
>>
>>
>> Silly me. root=UUID= has nothing to do with udev, but `blkid` in
>> util-linux. At least that's how it's done in Arch/mkinitcpio.
>>
>
> The rule is "don't break working systems", not "but we are allowed to break
> systems, see it says here not to depend on this"
>
> Drive ordering has been stable since the 0.1 kernel [1]
>
> It takes a lot longer to detect USB drives, why in the world would they be
> detected before hard-wired drives?
>
> I expect that Linus' response is going to be very quotable.
>
> David Lang
>
>
> [1] given stable hardware and no new drivers becoming involved