linux-kernel - Re: [patch] err.h: IS_ERR() can accept _

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

Message-Id: <20130508151622.87bde6d58f96ddca9561541f@linux-foundation.org>
Date:	Wed, 8 May 2013 15:16:22 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	linux-kernel@...r.kernel.org, Christopher Li <sparse@...isli.org>
Subject: Re: [patch] err.h: IS_ERR() can accept __user pointers

On Wed, 8 May 2013 10:42:22 +0300 Dan Carpenter <dan.carpenter@...cle.com> wrote:

> Sparse generates a false positive when you pass a __user or __iomem
> pointer to the IS_ERR() functions.
> 
> drivers/rtc/rtc-ds1286.c:344:36: sparse: incorrect type in argument 1 (different address spaces)
> drivers/rtc/rtc-ds1286.c:344:36:    expected void const *ptr
> drivers/rtc/rtc-ds1286.c:344:36:    got unsigned int [noderef] [usertype] <asn:2>*rtcregs
> 
> We can silence these by adding a __force here and upgrading to the
> latest git release of Sparse.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@...cle.com>
> ---
> This change has no effect when using current Sparse releases.

You often put really important stuff after the ^--- and I always move
it to before the ^--- :)

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