On Wed, Dec 14, 2005 at 01:15:55PM +0100, Blaisorblade wrote:
> As a fix, I suggest switching away from printk() for such early uses. Do you
> agree? I wonder if that's enough, but hey, the rule is "no spinlock without
> kernel stack". And then it seems correct the printk() avoidance.
Yes, this occurred to me later - printk (and any other kernel stuff) should
not run on the initial stack. I've tried to be careful about this, but we
seem to have missed some things. printf should be used on the initial stack,
printk should be used on kernel stacks, and neither should be used elsewhere.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
