linux-kernel - Re: Implement complete

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]

Message-ID: <20161028093709.2e931e34@gandalf.local.home>
Date:   Fri, 28 Oct 2016 09:37:09 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Daniel Wagner <wagi@...om.org>
Cc:     linux-rt-users@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Christoph Hellwig <hch@....de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Nicholas Mc Guire <der.herr@...r.at>
Subject: Re: Implement complete_all() with swait

On Fri, 28 Oct 2016 09:17:04 +0200
Daniel Wagner <wagi@...om.org> wrote:

> 
> So I went through the list of users and tried to identify which of them 
> is going to make troubles. I found 4 users which are using 
> complete_all() while IRQs are disabled. The rest looks like it just 
> would work nice. I already fixed up a bunch of drivers which use 
> complete_all() just to make really sure the single waiter is woken up. 
> This list does only contain proper complete_all() users.
> 

I wonder if we can just create a separate thread or workqueue that
performs the complete all, and have the callers of complete_all() that
are currently under irqs disabled simply wake up the thread/workqueue
to perform the complete_all() with interrupts enabled?

-- Steve