linux-kernel - Re: [PATCH v3] kthread: Work could not be queued when worker being destroyed

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]

Message-ID: <20200706145945.GB5603@mtj.thefacebook.com>
Date:   Mon, 6 Jul 2020 10:59:45 -0400
From:   Tejun Heo <tj@...nel.org>
To:     qiang.zhang@...driver.com
Cc:     ben.dooks@...ethink.co.uk, bfields@...hat.com, cl@...k-chips.com,
        peterz@...radead.org, pmladek@...e.com, akpm@...ux-foundation.org,
        mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] kthread: Work could not be queued when worker being
 destroyed

On Sun, Jul 05, 2020 at 09:30:18AM +0800, qiang.zhang@...driver.com wrote:
> From: Zhang Qiang <qiang.zhang@...driver.com>
> 
> Before the work is put into the queue of the worker thread,
> the state of the worker thread needs to be detected,because
> the worker thread may be in the destruction state at this time.
> 
> Signed-off-by: Zhang Qiang <qiang.zhang@...driver.com>
> Suggested-by: Petr Mladek <pmladek@...e.com>
> Reviewed-by: Petr Mladek <pmladek@...e.com>

Andrew already brought this up but can you please provide some context on
why you're making this change?

Thanks.

-- 
tejun