Re: [PATCH] powerpc/vdso: Fix multiple issues with sys_call_table

2021-06-10 Thread Christophe Leroy
Le 19/03/2020 à 02:10, Michael Ellerman a écrit : Anton Blanchard writes: The VDSO exports a bitmap of valid syscalls. vdso_setup_syscall_map() sets this up, but there are both little and big endian bugs. The issue is with: if (sys_call_table[i] != sys_ni_syscall) On little endian,

Re: [PATCH] powerpc/vdso: Fix multiple issues with sys_call_table

2020-03-18 Thread Michael Ellerman
Anton Blanchard writes: > The VDSO exports a bitmap of valid syscalls. vdso_setup_syscall_map() > sets this up, but there are both little and big endian bugs. The issue > is with: > >if (sys_call_table[i] != sys_ni_syscall) > > On little endian, instead of comparing pointers to the two fun

Re: [PATCH] powerpc/vdso: Fix multiple issues with sys_call_table

2020-03-18 Thread kbuild test robot
Hi Anton, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on powerpc/next] [also build test WARNING on linux/master linus/master v5.6-rc6 next-20200317] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also

[PATCH] powerpc/vdso: Fix multiple issues with sys_call_table

2020-03-05 Thread Anton Blanchard
The VDSO exports a bitmap of valid syscalls. vdso_setup_syscall_map() sets this up, but there are both little and big endian bugs. The issue is with: if (sys_call_table[i] != sys_ni_syscall) On little endian, instead of comparing pointers to the two functions, we compare the first two inst