linux-kernel - Re: [PATCH] for account_group_exec_runtime(), make sure ->signal can't be freed under rq->lock

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Nov 2008 11:35:32 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Oleg Nesterov <oleg@...hat.com>, Frank Mayhar <fmayhar@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>, adobriyan@...il.com,
	Doug Chapman <doug.chapman@...com>,
	Roland McGrath <roland@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] for account_group_exec_runtime(), make sure ->signal
	can't be freed under rq->lock

* Oleg Nesterov <oleg@...hat.com> wrote:

> The patch is ugly, but I don't see the better fix for now. Needs the 
> review from Peter/Ingo.

this is indeed too ugly, and if we do it we'll get both this ugliness 
and the CPU loop upstream forever. Frank, if you dont have time to fix 
this code, then i guess the best thing is to do the full revert that 
Peter sent.

Regarding this teardown bug. Stupid question: why cannot the signal 
structure live as long as the last user is around? It's a tiny amount 
of RAM.

	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/