linux-kernel - Re: fork() && ftrace_graph_exit

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: <20090524221615.GG6471@nowhere>
Date:	Mon, 25 May 2009 00:16:16 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: fork() && ftrace_graph_exit_task()

On Thu, May 21, 2009 at 09:53:30PM +0200, Oleg Nesterov wrote:
> What if the task with ->ret_stack != NULL calls fork(), and
> copy_prcoess() fails after successfull dup_task_struct() ?
> 
> bad_fork_free: -> free_task()->ftrace_graph_exit_task() will
> free the parent's ->ret_stack copied by arch_dup_task_struct(),
> no?
> 
> Oleg.
>


Good catch, that's a rare situation but very dangerous.

I will fix it, thanks for your report!

Frederic.

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