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>] [day] [month] [year] [list]
Message-ID: <39a56b046b104566922dd0d0ce7f794a@AcuMS.aculab.com>
Date:   Mon, 7 Sep 2020 08:49:27 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Christoph Hellwig' <hch@....de>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        Palmer Dabbelt <palmer@...belt.com>,
        "Arnd Bergmann" <arnd@...db.de>,
        Alexander Viro <viro@...iv.linux.org.uk>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Using asm_volatile_goto for get_user()

I had an idea that might let 'asm_volatile_goto' be used for
get_user() even though gcc doesn't allow outputs.

What if (eg) 'register eax asm ("eax") is used for the
output and (probably) given in the 'clobber' list.

Such variables are usually used to get explicit registers
used when there is no suitable constraint.
I don't see why it shouldn't work for 'asm goto' as well
as just 'asm'.

While this forces the read value into a specific register
that probably doesn't make much difference to the code.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ