linux-kernel - Re: Too async libata breakage

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] [day] [month] [year] [list]

Message-ID: <20090108112840.46e3f063@infradead.org>
Date:	Thu, 8 Jan 2009 11:28:40 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Alexey Dobriyan" <adobriyan@...il.com>
Cc:	torvalds@...l.org, "Linux Kernel" <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org
Subject: Re: Too async libata breakage

On Thu, 8 Jan 2009 22:15:56 +0300
"Alexey Dobriyan" <adobriyan@...il.com> wrote:

> commit f29d3b23238e1955a8094e038c72546e99308e61 aka
> "fastboot: Make libata initialization even more async"
> results in no findable /dev/sda2 to mount / here.
> 
> Kernel correctly sees sda as 750GB drive and the rest too.
> 
> CONFIG_ATA_PIIX is in use, everything built-in, plain partitions,
> no initrd, DM, MD etc.

hmm. 
no initrd; 

can you try an experiment?
if you edit init/do_mounts.c and find the "async_synchronize_full" call.
that is just after a while() loop. 
Can you put another call to synchronize_full to also just before that
while loop and see if that fixes it ?

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/