linux-ext4 - Re: one way to dmesg

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

Message-ID: <1257347955.2852.13.camel@zwerg>
Date:	Wed, 04 Nov 2009 16:19:15 +0100
From:	Alexey Fisher <bug-track@...her-privat.net>
To:	linux-ext4@...r.kernel.org
Subject: Re: one way to dmesg

Am Mittwoch, den 04.11.2009, 15:26 +0100 schrieb Alexey Fisher:
> Hallo,
> this is sort of continue of discussion about unified way to mount fs
> readonly.
> I wont to know how about dmesg/printk. I see ext[234] produce different
> logs on mount even it use same code. I feel like i have some time to
> digg in. My target is easy to parse dmesg.
> Firs question: is it really important to print function in ext3_warning?
> Or is it just ok to do it ext4_msg way?
Ok forgot this question, i found ext4_warning. So i will just add
ext2_msg and ext3_msg

Regards,
Alexey

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html