linux-kernel - Re: [PATCH] Fix uninitialized spinlock of printk

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:	Wed, 19 May 2010 13:26:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] Fix uninitialized spinlock of printk_ratelimited()

On Mon, 17 May 2010 08:57:38 +0900
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> wrote:

> ratelimit_state initialization of printk_ratelimited() seems
> broken. This fixes it by using DEFINE_RATELIMIT_STATE() to initialize
> spinlock properly.
> 
> Signed-off-by: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
> ---
> 
>  include/linux/kernel.h |   15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff -puN include/linux/kernel.h~printk_ratelimited-fix include/linux/kernel.h
> --- linux-2.6/include/linux/kernel.h~printk_ratelimited-fix	2010-05-17 03:37:33.000000000 +0900
> +++ linux-2.6-hirofumi/include/linux/kernel.h	2010-05-17 03:37:33.000000000 +0900
> @@ -420,14 +420,13 @@ static inline char *pack_hex_byte(char *
>   * no local ratelimit_state used in the !PRINTK case
>   */
>  #ifdef CONFIG_PRINTK
> -#define printk_ratelimited(fmt, ...)  ({		\
> -	static struct ratelimit_state _rs = {		\
> -		.interval = DEFAULT_RATELIMIT_INTERVAL, \
> -		.burst = DEFAULT_RATELIMIT_BURST,       \
> -	};                                              \
> -							\
> -	if (__ratelimit(&_rs))                          \
> -		printk(fmt, ##__VA_ARGS__);		\
> +#define printk_ratelimited(fmt, ...)  ({				\
> +	static DEFINE_RATELIMIT_STATE(_rs,				\
> +				      DEFAULT_RATELIMIT_INTERVAL,	\
> +				      DEFAULT_RATELIMIT_BURST);		\
> +									\
> +	if (__ratelimit(&_rs))						\
> +		printk(fmt, ##__VA_ARGS__);				\
>  })

hm, yes, that spinlock will get the all-zeroes pattern.

It's been like this since December 2009.  I'm a bit surprised that none
of our spinlock-debugging goodies picked this up.  All the
CONFIG_DEBUG_SPINLOCK spinlock fields end up zeroed out also.

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