uaccess: fix type mismatch warnings from access_ok()
On some architectures, access_ok() does not do any argument type checking, so replacing the definition with a generic one causes a few warnings for harmless issues that were never caught before. Fix the ones that I found either through my own test builds or that were reported by the 0-day bot. Reported-by:kernel test robot <lkp@intel.com> Reviewed-by:
Christoph Hellwig <hch@lst.de> Acked-by:
Dinh Nguyen <dinguyen@kernel.org> Signed-off-by:
Arnd Bergmann <arnd@arndb.de>
Showing
- arch/arc/kernel/process.c 1 addition, 1 deletionarch/arc/kernel/process.c
- arch/arm/kernel/swp_emulate.c 1 addition, 1 deletionarch/arm/kernel/swp_emulate.c
- arch/arm/kernel/traps.c 1 addition, 1 deletionarch/arm/kernel/traps.c
- arch/csky/kernel/perf_callchain.c 1 addition, 1 deletionarch/csky/kernel/perf_callchain.c
- arch/csky/kernel/signal.c 1 addition, 1 deletionarch/csky/kernel/signal.c
- arch/nios2/kernel/signal.c 11 additions, 9 deletionsarch/nios2/kernel/signal.c
- arch/powerpc/lib/sstep.c 2 additions, 2 deletionsarch/powerpc/lib/sstep.c
- arch/riscv/kernel/perf_callchain.c 2 additions, 2 deletionsarch/riscv/kernel/perf_callchain.c
- arch/sparc/kernel/signal_32.c 1 addition, 1 deletionarch/sparc/kernel/signal_32.c
- lib/test_lockup.c 2 additions, 2 deletionslib/test_lockup.c
Please register or sign in to comment