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]
Date:   Fri, 20 Aug 2021 13:05:30 +0200
From:   Arnd Bergmann <arnd@...nel.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        "moderated list:H8/300 ARCHITECTURE" 
        <uclinux-h8-devel@...ts.sourceforge.jp>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: remove set_fs() for h8300

On Tue, Aug 17, 2021 at 7:21 AM Christoph Hellwig <hch@....de> wrote:
>
> On Fri, Jul 09, 2021 at 01:53:09PM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series removes support for the deprecated set_fs address space
> > override on h8300.  Because h8300 doesn't actually have different
> > address spaces to start with as a pure nommu port the changes are
> > pretty simple.
> >
> > Compile tested only.
>
> Any comments?

It took me a while to figure out that this works on architectures that
define CONFIG_UACCESS_MEMCPY, as they get the asm-generic
version of get_kernel_nofault(). Maybe add that to the changelog,
plus my

Reviewed-by: Arnd Bergmann <arnd@...db.de>

Do you have more of these? I'm happy to take them through the
asm-generic tree, at least for architectures with no response from
the maintainers (not m68k, which looks too complex). I did partial
patches for sh and sparc at some point to remove the set_fs() callers,
but got stuck when I tried doing ia64 and didn't submit any of these.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ