[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjXFfeCHdhAwH8ciXhMJwAc3dOnCAug4G8=eb=+zFnkTQ@mail.gmail.com>
Date: Sun, 20 Dec 2020 10:51:53 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Peter Anvin <hpa@...or.com>
Cc: Heiko Carstens <hca@...ux.ibm.com>,
Arnd Bergmann <arnd@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Matthew Wilcox <willy@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ibm.com>,
"David S. Miller" <davem@...emloft.net>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [PATCH] epoll: fix compat syscall wire up of epoll_pwait2
On Sun, Dec 20, 2020 at 10:22 AM Willem de Bruijn
<willemdebruijn.kernel@...il.com> wrote:
>
> Slightly tangential, it's not immediately clear to me why in
> arch/x86/entry/syscalls/syscall_32.tbl epoll_pwait does not need a
> compat entry, unlike on other architectures and unlike signalfd.
Hmm. Good question. That looks like a bug to me. Probably nobody
noticed because it's so rarely used.
Or maybe I'm missing something too.
Adding x86 entry code people to the participants.
Linus
Powered by blists - more mailing lists