Subject: Re: printk in init_module mixing with printf in insmod
To: dank@kegel.com
Date: Fri, 19 Apr 2002 23:24:51 +0100 (BST)
Cc: linux-kernel@vger.kernel.org (linux-kernel@vger.kernel.org)
In-Reply-To: <3CC06470.F05543C4@kegel.com> from "Dan Kegel" at Apr 19, 2002 11:39:44 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E16ygoF-000831-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

>   printk("Hello, world\n");
> in the module are intermixed unpleasantly, yielding output like
>     Warning: loHello,ading foo.o world
>     will taint kernel
> 
> This garbled output makes reading the debugging printk's difficult.
> 
> I suppose this isn't terribly important, since printk's are
> kind of a no-no in production, and this only affects printk's
> in init_module, but it'd be nice to know what
> the cleanest way to get rid of the mixing is.  Adding a sleep
> inside insmod seems heavyhanded.  I suppose I could redirect
> insmod's output to a file, sleep a bit, and then display the 
> file... bleah.

Probably you want to fprintf the message after the module initialise has
reported completion, instead of before. I see no good way of hiding it
the other way around.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/