Re: [PATCH 1/9] kernel: add a PF_FORCE_COMPAT flag
From: Al Viro <viro@zeniv.linux.org.uk>
Date: 2020-09-20 21:42:49
Also in:
io-uring, keyrings, linux-arch, linux-arm-kernel, linux-block, linux-fsdevel, linux-mips, linux-mm, linux-s390, linux-scsi, linux-security-module, linuxppc-dev, lkml, sparclinux
On Sun, Sep 20, 2020 at 08:22:59PM +0100, Matthew Wilcox wrote:
On Sun, Sep 20, 2020 at 08:10:31PM +0100, Al Viro wrote:quoted
IMO it's much saner to mark those and refuse to touch them from io_uring...Simpler solution is to remove io_uring from the 32-bit syscall list. If you're a 32-bit process, you don't get to use io_uring. Would any real users actually care about that?
What for? I mean, is there any reason to try and keep those bugs as first-class citizens? IDGI... Yes, we have several special files (out of thousands) that have read()/write() user-visible semantics broken wrt 32bit/64bit. And we have to keep them working that way for existing syscalls. Why would we want to pretend that their behaviour is normal and isn't an ABI bug, not to be repeated for anything new?