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  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]
Date:   Fri, 8 Jan 2021 23:08:58 +0000
From:   "Luck, Tony" <>
To:     Peter Zijlstra <>
CC:     Borislav Petkov <>, "" <>,
        "Andrew Morton" <>,
        Darren Hart <>,
        Andy Lutomirski <>,
        "" <>,
        "" <>,
        "" <>
Subject: RE: [PATCH 2/2] futex, x86/mce: Avoid double machine checks

> I think this is horrid; why can't we have it return something different
> then -EFAULT instead?

I did consider this ... but it appears that architectures aren't unified in the
return value from get_user()

Here's another function involved in the futex call chain leading to this:

static int get_futex_value_locked(u32 *dest, u32 __user *from)
        int ret;

        ret = __get_user(*dest, from);

        return ret ? -EFAULT : 0;

It seems like the expectation here is just "zero or not" and we
don't care what the "not" value is ... just turn it into -EFAULT.


Powered by blists - more mailing lists