linux-kernel - Re: [PATCH v3 4/4] compat: remove some compat entry points

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 20 May 2021 11:21:12 +0200
From:   Arnd Bergmann <arnd@...nel.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     linux-arch <linux-arch@...r.kernel.org>,
        Christoph Hellwig <hch@...radead.org>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Borislav Petkov <bp@...en8.de>,
        Brian Gerst <brgerst@...il.com>,
        Eric Biederman <ebiederm@...ssion.com>,
        Ingo Molnar <mingo@...nel.org>,
        "H. Peter Anvin" <hpa@...or.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>, kexec@...ts.infradead.org
Subject: Re: [PATCH v3 4/4] compat: remove some compat entry points

On Wed, May 19, 2021 at 11:00 PM Arnd Bergmann <arnd@...nel.org> wrote:
>
> On Wed, May 19, 2021 at 10:33 PM Thomas Gleixner <tglx@...utronix.de> wrote:
> >
> > On Mon, May 17 2021 at 22:33, Arnd Bergmann wrote:
> > > From: Arnd Bergmann <arnd@...db.de>
> > >
> > > These are all handled correctly when calling the native
> > > system call entry point, so remove the special cases.
> > >  arch/x86/entry/syscall_x32.c              |  2 ++
> > >  arch/x86/entry/syscalls/syscall_32.tbl    |  6 ++--
> > >  arch/x86/entry/syscalls/syscall_64.tbl    |  4 +--
> >
> > That conflicts with
> >
> >   https://lore.kernel.org/lkml/20210517073815.97426-1-masahiroy@kernel.org/
> >
> > which I'm picking up. We have more changes in that area coming in.
>
> Ok, thanks for the heads-up. I'll try a merge or rebase to see how this can be
> handled. If both the drivers/net and drivers/media get picked up for 5.14, maybe
> the rebased patches can go through -mm on top, along with the final
> removal of compat_alloc_user_space()/copy_in_user(). If not, I suppose these
> four patches can also wait another release.

On second thought, this patch 4/4 is not even required here to kill off
compat_alloc_user_space, so the easiest alternative might be to merge the
other patches first, and then do this part together with the removal of
the unused functions in a follow-up series.

        Arnd