linux-kernel - Re: [RFC/PATCH] ratelimit: make output more useful

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Oct 2009 14:17:10 -0700
From:	Joe Perches <joe@...ches.com>
To:	Christian Borntraeger <borntraeger@...ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Young <hidave.darkstar@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC/PATCH] ratelimit: make output more useful

On Fri, 2009-10-23 at 17:12 +0200, Christian Borntraeger wrote:
> Am Freitag 23 Oktober 2009 16:55:09 schrieb Ingo Molnar:
> > Any reason why it couldnt be pushed inside printk.c? We just need the
> > func string - not the pointer pass-in. That would also address some of
> > the call-site bloat.

[]

> +extern int __printk_ratelimit(const char *func);
> +#define printk_ratelimit() __printk_ratelimit(__func__)

Perhaps check if CONFIG_KALLSYMS is defined and use

%pS ... __builtin_return_address(0) ?


--
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/