linux-kernel - Re: preempt_schedule

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: <4d97b838-6e49-4bba-1c9e-6bf51db3e3a2@arm.com>
Date:   Wed, 16 Jan 2019 15:23:28 +0000
From:   Valentin Schneider <valentin.schneider@....com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     Ingo Molnar <mingo@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will.deacon@....com>,
        Mark Rutland <mark.rutland@....com>,
        Julien Thierry <julien.thierry@....com>
Subject: Re: preempt_schedule_irq() loop question

On 16/01/2019 14:57, Thomas Gleixner wrote:
[...]
> 
> I just went back in the history tree and had to figure out that it's my
> fault :)
> 
> preempt_schedule_irq() was introduced to plug a stupid race, but I did not
> notice (and obviously nobody else) that this made the extra loop in the
> entry code pointless. So it's just histerical raisins without any value.
> 

I see, thanks for clearing that up! Credit goes to Julien & Will for
unearthing the oddity.

> Thanks,
> 
> 	tglx
>