From: Andrew Morton <akpm@linux-foundation.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] init: make sure syscall arguments are marked __user where needed
Date: Fri, 20 Apr 2012 17:43:19 -0700 [thread overview]
Message-ID: <20120420174319.6cea0e81.akpm@linux-foundation.org> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F002069887E112@AUSP01VMBX24.collaborationhost.net>
On Fri, 20 Apr 2012 19:05:46 -0500 H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> > Can we just make "make C=1" skip that file or something?
>
> What about putting something like this at the top of the files:
>
>
> /*
> * Many of the syscalls used in this file expect some of the arguments
> * to be __user pointers not __kernel pointers. To limit the sparse
> * noise, turn off sparse checking for this file.
> */
> #ifdef __CHECKER__
> #undef __CHECKER__
> #warning "Sparse checking disabled for this file"
> #endif
>
>
> Maybe without the warning if it doesn't seem necessary.
>
> This keeps <linux/compiler.h> from defining the __attribute__* checks.
That looks nice and explicit.
next prev parent reply other threads:[~2012-04-21 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 0:33 [RFC PATCH 0/2] init: make sure syscall arguments are marked __user where needed H Hartley Sweeten
2012-04-20 23:00 ` Andrew Morton
2012-04-21 0:05 ` H Hartley Sweeten
2012-04-21 0:43 ` Andrew Morton [this message]
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=20120420174319.6cea0e81.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hartleys@visionengravers.com \
--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.