linux-kernel - Re: [PATCH] async: Using current_work() to implement current_is

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: <8336ea6a-bc98-bd45-b317-3fc8d5f1d9f8@acm.org>
Date:   Thu, 26 Sep 2019 08:27:13 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     Yunfeng Ye <yeyunfeng@...wei.com>,
        Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        bhelgaas@...gle.com, dsterba@...e.com,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        sakari.ailus@...ux.intel.com
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] async: Using current_work() to implement
 current_is_async()

On 9/26/19 1:40 AM, Yunfeng Ye wrote:
> current_is_async() can be implemented using current_work(), it's better
> not to be aware of the workqueue's internal information.

Reviewed-by: Bart Van Assche <bvanassche@....org>