linux-kernel - Re: [PATCH v2] 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] [day] [month] [year] [list]

Date:   Fri, 3 Jul 2020 12:13:30 -0700
From:   Andrew Morton <akpm@...ux-foundation.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>,
        <tj@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] kthread: work could not be queued when worker being
 destroyed

On Thu, 2 Jul 2020 15:01:56 +0800 <qiang.zhang@...driver.com> wrote:

> From: Zhang Qiang <qiang.zhang@...driver.com>
> 
> The "queuing_blocked" func should print warning message and
> returns true when the worker being destroyed.

Why should it do this?

Please prepare a changelog which contains much more information.