Thread (75 messages) 75 messages, 14 authors, 2022-02-25

Re: [PATCH v2 12/18] uaccess: fix type mismatch warnings from access_ok()

From: Dinh Nguyen <dinguyen@kernel.org>
Date: 2022-02-25 04:30:49
Also in: linux-alpha, linux-api, linux-arch, linux-m68k, linux-mips, linux-mm, linux-riscv, linux-s390, linux-sh, linux-um, lkml, sparclinux


On 2/16/22 07:13, Arnd Bergmann wrote:
From: Arnd Bergmann <arnd@arndb.de>

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 <redacted>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
  arch/arc/kernel/process.c           |  2 +-
  arch/arm/kernel/swp_emulate.c       |  2 +-
  arch/arm/kernel/traps.c             |  2 +-
  arch/csky/kernel/signal.c           |  2 +-
  arch/mips/sibyte/common/sb_tbprof.c |  6 +++---
  arch/nios2/kernel/signal.c          | 20 +++++++++++---------
Acked-by: Dinh Nguyen <dinguyen@kernel.org>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help