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: <5a319c56-c165-5465-2dc6-4b0e08510abe@intel.com>
Date:   Mon, 19 Nov 2018 07:08:44 -0800
From:   Dave Hansen <dave.hansen@...el.com>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     Borislav Petkov <bp@...en8.de>, x86@...nel.org,
        Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        Andy Lutomirski <luto@...nel.org>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        kvm@...r.kernel.org, "Jason A. Donenfeld" <Jason@...c4.com>,
        Rik van Riel <riel@...riel.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] x86/fpu: Disable BH while while loading FPU registers in
 __fpu__restore_sig()

On 11/19/18 7:06 AM, Sebastian Andrzej Siewior wrote:
> On 2018-11-19 07:04:35 [-0800], Dave Hansen wrote:
>> Does the local_bh_disable() itself survive?
> Not in __fpu__restore_sig(). I do have:
> | static inline void __fpregs_changes_begin(void)
> | {
> |        preempt_disable();
> |        local_bh_disable();
> | }
> 
> and __fpregs_changes_begin() is introduced as part of the series.

OK, so can we just comment *that*, please?  Basically, why do we need botj?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ