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] [day] [month] [year] [list]
Date:   Wed, 06 May 2020 10:44:07 -0500
From: (Eric W. Biederman)
To:     Christoph Hellwig <>
Cc:     Linus Torvalds <>,
        Andrew Morton <>,
        Alexander Viro <>,
        Jeremy Kerr <>, Arnd Bergmann <>,
        Oleg Nesterov <>,
        the arch/x86 maintainers <>,
        linuxppc-dev <>,
        linux-fsdevel <>,
        Linux Kernel Mailing List <>
Subject: Re: remove set_fs calls from the coredump code v6

Christoph Hellwig <> writes:

> On Tue, May 05, 2020 at 03:28:50PM -0500, Eric W. Biederman wrote:
>> We probably can.   After introducing a kernel_compat_siginfo that is
>> the size that userspace actually would need.
>> It isn't something I want to mess with until this code gets merged, as I
>> think the set_fs cleanups are more important.
>> Christoph made some good points about how ugly the #ifdefs are in
>> the generic copy_siginfo_to_user32 implementation.
> Take a look at the series you are replying to, the magic x86 ifdefs are
> entirely gone from the common code :)


That is a different way of achieving that, and I don't hate it.
I still want whatever you are doing to settle before I touch that code
again.  Removing the set_fs is important and I have other fish to fry
at the moment.


Powered by blists - more mailing lists