From: H Hartley Sweeten <hartleys@visionengravers.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: <akpm@linux-foundation.org>
Subject: [RFC PATCH 0/2] init: make sure syscall arguments are marked __user where needed
Date: Mon, 16 Apr 2012 17:33:23 -0700 [thread overview]
Message-ID: <201204161733.23830.hartleys@visionengravers.com> (raw)
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@visionengravers.com>
Cc: Andrew Morton <akpm@linux-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(-)
next reply other threads:[~2012-04-17 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 0:33 H Hartley Sweeten [this message]
2012-04-20 23:00 ` [RFC PATCH 0/2] init: make sure syscall arguments are marked __user where needed Andrew Morton
2012-04-21 0:05 ` H Hartley Sweeten
2012-04-21 0:43 ` Andrew Morton
2012-04-21 0:46 ` H Hartley Sweeten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201204161733.23830.hartleys@visionengravers.com \
--to=hartleys@visionengravers.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.