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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 27 Sep 2019 09:01:30 +0800
From:   Yunfeng Ye <yeyunfeng@...wei.com>
To:     Bart Van Assche <bvanassche@....org>,
        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 2019/9/26 23:27, Bart Van Assche wrote:
> 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>
> 
I will update the patch with Reviewed-by, thanks.
> .
>