linux-kernel - Re: [PATCH] workqueue: Implement delayed_work

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-next>] [day] [month] [year] [list]

Message-ID: <20170524200141.GM24798@htj.duckdns.org>
Date:   Wed, 24 May 2017 16:01:41 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Alex Naidis <alex.naidis@...ux.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] workqueue: Implement delayed_work_busy()

Hello, Alex.

On Wed, May 24, 2017 at 09:58:19PM +0200, Alex Naidis wrote:
> Yeah, I agree, it is wrong to rely on work_busy() providing correct data.
> However sometimes it is useful to have an indicator like this to at least
> catch some cases where requeuing work would be obsolete.
> This applies for delayed work too.

Can you elaborage on "requeueing work would be obsolate" a bit?

Thanks.

-- 
tejun