linux-kernel - Re: USB storage no-boot regression (bisected)

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: <Pine.LNX.4.44L0.0904151146210.3072-100000@iolanthe.rowland.org>
Date:	Wed, 15 Apr 2009 11:47:38 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	Mark Lord <lkml@....ca>, Greg KH <greg@...ah.com>,
	Jeff Garzik <jeff@...zik.org>,
	Linux USB kernel mailing list <linux-usb@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: USB storage no-boot regression (bisected)

On Wed, 15 Apr 2009, Alan Cox wrote:

> Why should every user suffer a slower boot and a poorer resume time ?
> 
> Instead make the root fs mounting look like this
> 
> 
> 	while(my_rootfs_hasnt_appeared_and_i_am_sad()) {
> 		wait_on(&new_disk_discovery);
> 	}
> 
> and poke the queue whenever we add a relevant device.
> 
> That way if you are booting off an initrd you can finish the SATA probe
> in parallel to getting userspace ticking over.
> 
> On what is nowdays essentially a hot plug system it all needs turning
> this way up - eg RAID volumes should assemble and come online as the
> drives are discovered not at some fixed point later in userspace.

Indeed, something like this should also be used for 
resume-from-hibernation, to wait for the swap device.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/