linux-kernel - Re: [PATCH] rt-mutex: fixup rt-mutex debug code

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: <20061012184244.GA27879@elte.hu>
Date:	Thu, 12 Oct 2006 20:42:44 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] rt-mutex: fixup rt-mutex debug code


* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> BUG: warning at kernel/rtmutex-debug.c:125/rt_mutex_debug_task_free() (Not tainted)
>  [<c04051e3>] show_trace_log_lvl+0x58/0x16a
>  [<c04057f0>] show_trace+0xd/0x10
>  [<c0405900>] dump_stack+0x19/0x1b
>  [<c043f03d>] rt_mutex_debug_task_free+0x35/0x6a
>  [<c04224c0>] free_task+0x15/0x24
>  [<c042378c>] copy_process+0x12bd/0x1324
>  [<c0423835>] do_fork+0x42/0x113
>  [<c04021dd>] sys_fork+0x19/0x1b
>  [<c0403fb7>] syscall_call+0x7/0xb
> 
> In copy_process(), dup_task_struct() also duplicates the ->pi_lock, 
> ->pi_waiters and ->pi_blocked_on members. rt_mutex_debug_task_free() 
> called from free_task() validates these members. However free_task() 
> can be invoked before these members are reset for the new task.
> 
> Move the initialization code before the first bail that can hit 
> free_task().
> 
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>

thanks for tracking this one down!

Acked-by: Ingo Molnar <mingo@...e.hu>

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