linux-kernel - Re: Print long messages to console from kernel module

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: <47C81DA6.8040100@enea.com>
Date:	Fri, 29 Feb 2008 15:58:46 +0100
From:	Arvid Brodin <arvid.brodin@...a.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Print long messages to console from kernel module

Things have cleared a bit. First, my problem is with printing to console.
Second, the date-time-host header is only appended when using loglevel
KERN_DEBUG. Third, the <n> tag is only appended to the beginning of the printk
printout if the last printout did not end with a '\n'. The whole printk code is
quite confuscated IMO, not the least so call_console_drivers(), so this could be
a feature, however it looks to me like the loglevel tag is for internal use and
my guess is it should never be printed on the console at all.

I'll look into filing a bug report and patch for this. At the moment the best
solution seems to be to search through the log I want to print and cut the
printout after every '\n'. That should take care of most of the "<n>"'s.

-- 
Arvid Brodin
Enea LCC

On 2008-02-25 18:30, Arvid Brodin wrote:
> I need to write messages > 1023 characters long to the console from a module*. printk() is limited to 1023 characters, and splitting the message over several printk()'s results in a line break and "Month hh:mm:ss host kernel:" being inserted in my text.
> 
> I tried including <linux/console.h> and using the console_drivers declared there, but get
> "WARNING: "console_drivers" [<path>/log.ko] undefined!" when compiling and
> "insmod: error inserting 'log.ko': -1 Unknown symbol in module" when insmodding.
> 
> I guess this is because non EXPORT_SYMBOL'd symbols are only accessible to statically linked code, and not to modules? I see in printk.c that console_drivers is set up there, and I haven't been able to find any other interface to console_drivers.
> 
> In short: is there any way to print messages to the console from a kernel module, except printk()? Is opening /dev/tty and writing to it the way to go?
> 
> 
> * I'm writing an in-memory logger to be included in a module. The log can be several megabytes. The idea is to use SysRq to print the contents of the log to console after a kernel panic or otherwise when writing to disk might not work.
> 
--
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/