linux-kernel - Re: [RFC PATCH 0/2] init: make sure syscall arguments are marked _

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Apr 2012 17:43:19 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/2] init: make sure syscall arguments are marked
 __user where needed

On Fri, 20 Apr 2012 19:05:46 -0500 H Hartley Sweeten <hartleys@...ionengravers.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.
--
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/