lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 16 Apr 2012 17:33:23 -0700
From:	H Hartley Sweeten <hartleys@...ionengravers.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
CC:	<akpm@...ux-foundation.org>
Subject: [RFC PATCH 0/2] init: make sure syscall arguments are marked __user where needed

When using syscall routines in the kernel, some of the arguments
should be user pointers but are missing the __user markup. This
produces a number of sparse warnings of the format:    
  
warning: incorrect type in argument 1 (different address spaces)
   expected char [noderef] <asn:1>*dev_name
   got char *name 

Wrap the syscall routines in the private do_mounts.h header so that
the appropriate __user markups are added for the init mount code.

Signed-off-by: H Hartley Sweeten <hsweeten@...ionengravers.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>

init: introduce private syscall wrappers for non-user space pointers
init: use private syscall wrappers for non-user space pointers

 init/do_mounts.c        |   14 +++---
 init/do_mounts.h        |  107 ++++++++++++++++++++++++++++++++++++++++++++++-
 init/do_mounts_initrd.c |   28 ++++++------
 init/do_mounts_md.c     |    6 +-
 init/do_mounts_rd.c     |   22 +++++-----
 init/initramfs.c        |   54 ++++++++++++-----------
 init/noinitramfs.c      |    9 ++--
 7 files changed, 173 insertions(+), 67 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ