Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures

From
Arnd Bergmann <arnd@arndb.de>
Date
2019-01-22 09:37:33
Also in
linux-alpha, linux-arch, lkml
Reply to
Andy Lutomirski, 2019-01-18
On Fri, Jan 18, 2019 at 7:50 PM Andy Lutomirski [off-list ref] wrote:
On Fri, Jan 18, 2019 at 8:25 AM Arnd Bergmann [off-list ref] wrote:

I have a patch that I'll send soon to make x32 use its own table.  As
far as I'm concerned, 547 is *it*.  548 is just a normal number and is
not special.  But let's please not reuse 512..547 for other purposes
on x86 variants -- that way lies even more confusion, IMO.
(trimming Cc list, as this is getting a little off-topic most most)

Just so I understand: do you mean duplicating the .tbl file, or just
the resulting table of entry points?

In either way, how will that work with the new io_uring_setup()
system call that will have to use the compat entry point?
Are you planning to use the same syscall number as x86_64
but point it to the compat function, or do we still need a new
syscall number for x32 in the regular range?

       Arnd
Thread (64 messages) 64 messages, 9 authors, last reply 2019-01-25
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help