linux-kernel - Re: [PATCH] staging: lustre: Fix sparse warning on address-space

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: <20150117235355.GA23254@kroah.com>
Date:	Sat, 17 Jan 2015 15:53:55 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Jia He <hejianet@...il.com>
Cc:	linux-kernel@...r.kernel.org, Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH] staging: lustre: Fix sparse warning on address-space

On Mon, Dec 29, 2014 at 08:49:40PM +0800, Jia He wrote:
> This patch is to fix the below warnings generated by sparse:
>  warning: incorrect type in argument 1 (different address spaces)
>  expected void const volatile [noderef] <asn:1>*<noident>
>  got int *<noident>
> Adding the macro "__user" can suppress the warnings, and aslo some lines
> are adjusted for 80 chars line limitation.
> Already checked by sparse "C=2"
> 
> Signed-off-by: Jia He <hejianet@...il.com>
> Cc: Oleg Drokin <oleg.drokin@...el.com> 
> Cc: Andreas Dilger <andreas.dilger@...el.com> 
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> ---
>  .../staging/lustre/lustre/include/lprocfs_status.h | 18 ++++-----
>  .../lustre/lustre/obdclass/lprocfs_status.c        |  6 +--
>  drivers/staging/lustre/lustre/osc/lproc_osc.c      | 44 +++++++++++-----------
>  drivers/staging/lustre/lustre/osc/osc_request.c    |  6 +--
>  .../staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c    |  6 +--
>  5 files changed, 40 insertions(+), 40 deletions(-)

Doesn't apply to my staging-testing branch at all :(
--
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/