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 16:00:39 -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 Mon, 16 Apr 2012 17:33:23 -0700
H Hartley Sweeten <hartleys@...ionengravers.com> wrote:

> 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.

This makes rather a mess of do_mounts.c for pretty marginal benefit.

Can we just make "make C=1" skip that file or something?
--
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/