All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [bug report] lib/vdso: Provide generic VDSO implementation
Date: Thu, 27 Jun 2019 10:33:30 +0000	[thread overview]
Message-ID: <20190627103330.GA19015@kadam> (raw)
In-Reply-To: <20190627071521.GA22903@mwanda>

On Thu, Jun 27, 2019 at 12:26:06PM +0200, walter harms wrote:
> 
> 
> Am 27.06.2019 11:09, schrieb Vincenzo Frascino:
> > Hi Dan,
> > 
> > On 6/27/19 10:07 AM, Dan Carpenter wrote:
> >> On Thu, Jun 27, 2019 at 09:58:18AM +0100, Vincenzo Frascino wrote:
> >>>>    119	fallback:
> >>>>    120		return clock_gettime_fallback(clock, (struct __kernel_timespec *)res);
> >>>>                                                                                  ^^^
> >>>> On x86 this "res" always gets dereferenced.
> >>>>
> >>>>    121	}
> >>>>
> >>>
> >>> I am not sure I understand the details of this bug report. As far as I can see
> >>> "res" is never dereferenced in the vDSO library in this case, but it is passed
> >>> to the system call unchanged.
> >>>
> >>
> >> Oh yeah.  Sorry.  My bad.  False positive.  clock_gettime_fallback()
> >> doesn't necessarily dereference "res".
> >>
> > 
> > No problem, better a false positive than an ignored negative :-)
> > 
> 
> maybe it would be clever to add a comment here indicating that this
> is intended and no problem ?
> 

No.  The correct response is to fix Smatch.  I will do it.

regards,
dan carpenter

  parent reply	other threads:[~2019-06-27 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  7:15 [bug report] lib/vdso: Provide generic VDSO implementation Dan Carpenter
2019-06-27  7:18 ` Dan Carpenter
2019-06-27  8:58 ` Vincenzo Frascino
2019-06-27  9:07 ` Dan Carpenter
2019-06-27  9:09 ` Vincenzo Frascino
2019-06-27 10:26 ` walter harms
2019-06-27 10:33 ` Dan Carpenter [this message]
2019-06-27 10:36 ` Vincenzo Frascino

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=20190627103330.GA19015@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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.