linux-kernel - Re: [PATCH 1/3] stop_machine: check work->done while handling enqueued works

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]

Date:	Thu, 7 Feb 2013 08:37:39 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Hillf Danton <dhillf@...il.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] stop_machine: check work->done while handling
 enqueued works

Hello, Hillf.

On Thu, Feb 07, 2013 at 08:13:44PM +0800, Hillf Danton wrote:
> > If this is meant as a pure cleanup, I'm not sure it's an improvement.
> > You own your cpu_stop_done until you call cpu_stop_signal_done() on
> > it, so I don't think there's anything wrong with the current code.
> > The new code is different, not necessarily better.
> 
> The comment just above cpu_stop_signal_done()
> says it is not certain that the input done is valid, so
> I did this work.
> Plus works enqueued through stop_one_cpu_nowait()
> do carry no done.

So, are you saying that we can hit NULL deref in cpu_stopper_thread()
and this is a bug fix?  If so, can you please redo the description?  I
really can't tell what the patch is trying to do from the original
description.

Thanks.

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