linux-kernel - Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms))

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: <20061025165117.GD5675@ucw.cz>
Date:	Wed, 25 Oct 2006 16:51:17 +0000
From:	Pavel Machek <pavel@....cz>
To:	Andrew Morton <akpm@...l.org>
Cc:	rjw@...k.pl, linux-kernel@...r.kernel.org, greg@...ah.com
Subject: Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms))

Hi!

> > > > Sorry, I meant:
> > > > 
> > > > "sata is initialized *after* swsusp => bad".
> > > 
> > > Which patch made this change, and why?
> > 
> > CONFIG_PCI_MULTITHREAD_PROBE is the setting responsible, and IIRC
> > that's Greg's code.
> > 
> > Now... what is the recommended way to wait for hard disks to become
> > online?
> 
> The multithreaded probing is breaking (or at least altering) the initcall
> ordering guarantees.  We should wait for all the probing kernel threads to
> terminate after processing each initcall level.  

Can I read that as 'problem is bigger than swsusp, so someone else
(not Pavel :-) will solve it'?
							Pavel
-- 
Thanks for all the (sleeping) penguins.
-
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/