linux-kernel - Re: [PATCH] MMC: Flush mmc workqueue late in the boot sequence

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]

Date:	Sun, 13 May 2007 15:47:22 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	Pierre Ossman <drzeus@...eus.cx>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MMC: Flush mmc workqueue late in the boot sequence

On Sun, 13 May 2007 15:34:51 +0200
Pierre Ossman <drzeus@...eus.cx> wrote:

> > I'm not sure how many embedded people actually know how to build an
> > initrd for a custom board.
> >   
> 
> All the ones I have on my desk right now use initrd. ;)

Ok, I guess we'll just have to look into that, then.

> I had a chat with David Woodhouse and Segher Boessenkool and I think we have
> another approach. Basically, we move the waiting which would normally go into
> the initrd and move it into the kernel. So you get something like:
> 
> "Waiting for root device /dev/mmcblk0p1..."
> 
> The only problem here is if the device never shows up, but if that was the case
> you would previously get a panic, so it should not be any worse.

Indeed, it will even be pretty obvious what happened, and the user can
probably just insert a card at that point to get a working system.

> Does that sound like something that would work for you? From my point of view
> it's a much cleaner solution that has the benefit of not being tied into a
> certain subsystem (i.e. this would "fix" usb aswell).

Yes, that would definitely work.

Haavard
-
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/