All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Thu, 23 Mar 2017 16:30:29 -0300	[thread overview]
Message-ID: <20170323193028.GC22066@builder> (raw)
In-Reply-To: <20170329103405.GA4087@kroah.com>

On Wed, Mar 29, 2017 at 12:34:05PM +0200, Greg KH wrote:
> On Thu, Mar 23, 2017 at 04:09:03PM -0300, Marcos Paulo de Souza wrote:
> > On Wed, Mar 29, 2017 at 09:31:14AM +0200, Greg KH wrote:
> > > 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?
> > 
> > I don't know, it's my first sparse patch, so I tried to fix this
> > warning.
> > 
> > > 
> > > You also have a typo in your subject :(
> > 
> > Sorry, didn't noticed yesterday :(
> > 
> > > 
> > > > 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?
> > 
> > I didn't tested, it just removed the warning. Is this a false positive?
> 
> I don't know, it's up to you to prove to me that you know this change is
> correct.  You have to justify your changes, and "because checkpatch.pl
> complained" isn't a valid justification for something like this :)

Fair enough, I'll take in another sparse report to work on. Thanks!

> 
> thanks,
> 
> greg k-h

-- 
Thanks,
	Marcos

      reply	other threads:[~2017-03-29 10:50 UTC|newest]

Thread overview: 7+ 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 ` [lustre-devel] " Greg KH
2017-03-29  7:31   ` Greg KH
2017-03-23 19:09   ` Marcos Paulo de Souza
2017-03-29 10:34     ` [lustre-devel] " Greg KH
2017-03-29 10:34       ` Greg KH
2017-03-23 19:30       ` Marcos Paulo de Souza [this message]

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=20170323193028.GC22066@builder \
    --to=marcos.souza.org@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=doug.s.oucharek@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.