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]
Date:	Tue, 20 Mar 2012 09:47:03 +0100
From:	Jiri Slaby <>
To:	David Miller <>
Subject: Re: [PATCH 2/9] ext4: Use pr_fmt and pr_<level>

On 03/20/2012 08:10 AM, David Miller wrote:
> From:
> Date: Tue, 20 Mar 2012 01:46:06 -0400
>> OK. Say I'm a scraper.  How do I distinguish between:
>> pr_info("foo");
>> printk(KERN_INFO "foo");
>> Oh my. seems that both result in exactly the same thing ending up in the
>> dmesg buffer
> No it doesn't result in the same output, read the definitions again.
> pr_info can be influenced by pr_fmt, plain printk cannot

Ok, but how exactly does one select per-subsystem messages relying only
on pr_fmt?

Joe writes: "notify a particular set of per subsystem messages that
pr_<level> could easily provide"

Maybe the concept is not explained well enough that we do not follow?

suse labs
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists