Re: [PATCH 3/3] y2038: cobalt: posix/signal: Take care of compat mode for sigtimedwait64

2022-03-01 Thread Jan Kiszka via Xenomai
On 01.03.22 21:27, Florian Bezdeka wrote: > On 01.03.22 19:28, Jan Kiszka wrote: >> On 21.02.22 14:25, Florian Bezdeka wrote: >>> The compat syscall was previously routed to the native entrypoint. >>> While the timeout is always based on time64_t the siginfo has to be >>> handled different in

Re: [PATCH 3/3] y2038: cobalt: posix/signal: Take care of compat mode for sigtimedwait64

2022-03-01 Thread Florian Bezdeka via Xenomai
On 01.03.22 19:28, Jan Kiszka wrote: > On 21.02.22 14:25, Florian Bezdeka wrote: >> The compat syscall was previously routed to the native entrypoint. >> While the timeout is always based on time64_t the siginfo has to be >> handled different in compat mode. >> >> Signed-off-by: Florian Bezdeka

Re: [PATCH 3/3] y2038: cobalt: posix/signal: Take care of compat mode for sigtimedwait64

2022-03-01 Thread Jan Kiszka via Xenomai
On 21.02.22 14:25, Florian Bezdeka wrote: > The compat syscall was previously routed to the native entrypoint. > While the timeout is always based on time64_t the siginfo has to be > handled different in compat mode. > > Signed-off-by: Florian Bezdeka > --- >

[PATCH 3/3] y2038: cobalt: posix/signal: Take care of compat mode for sigtimedwait64

2022-02-21 Thread Florian Bezdeka via Xenomai
The compat syscall was previously routed to the native entrypoint. While the timeout is always based on time64_t the siginfo has to be handled different in compat mode. Signed-off-by: Florian Bezdeka --- kernel/cobalt/arch/x86/include/asm/xenomai/syscall32-table.h | 1 + 1 file changed, 1