From: Greg KH <gregkh@linuxfoundation.org>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: devel@driverdev.osuosl.org,
Doug Oucharek <doug.s.oucharek@intel.com>,
linux-kernel@vger.kernel.org, Oleg Drokin <oleg.drokin@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andreas Dilger <andreas.dilger@intel.com>,
lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lusten: conrpc.c: fix different address space sparse warning
Date: Wed, 29 Mar 2017 09:31:14 +0200 [thread overview]
Message-ID: <20170329073114.GA8459@kroah.com> (raw)
In-Reply-To: <20170329021409.24537-1-marcos.souza.org@gmail.com>
On Tue, Mar 28, 2017 at 11:14:06PM -0300, Marcos Paulo de Souza wrote:
> head_up parameter is marked with __user attribute, tmp is filled
> by a copy_from_user from next, that is also marked as __user, so
> tmp.next needs to be "casted" as __user to make sparse happy.
But is it the correct change?
You also have a typo in your subject :(
> Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
> ---
>
> this is mt first patch addressing an issue of sparse, so let me know
> if I misunderstood the error message
>
> drivers/staging/lustre/lnet/selftest/conrpc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/lustre/lnet/selftest/conrpc.c b/drivers/staging/lustre/lnet/selftest/conrpc.c
> index c6a683b..fb7ad74 100644
> --- a/drivers/staging/lustre/lnet/selftest/conrpc.c
> +++ b/drivers/staging/lustre/lnet/selftest/conrpc.c
> @@ -487,7 +487,7 @@ lstcon_rpc_trans_interpreter(struct lstcon_rpc_trans *trans,
> sizeof(struct list_head)))
> return -EFAULT;
>
> - if (tmp.next == head_up)
> + if ((struct list_head __user *)tmp.next == head_up)
Aer you sure this is correct? __user changes for lustre is not
trivial...
How did you test this?
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-29 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 2:14 [PATCH] staging: lusten: conrpc.c: fix different address space sparse warning Marcos Paulo de Souza
2017-03-29 7:31 ` Greg KH [this message]
2017-03-23 19:09 ` Marcos Paulo de Souza
2017-03-29 10:34 ` Greg KH
2017-03-23 19:30 ` Marcos Paulo de Souza
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=20170329073114.GA8459@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=doug.s.oucharek@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=marcos.souza.org@gmail.com \
--cc=oleg.drokin@intel.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).