All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Liming <liming.wang@windriver.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com
Subject: Re: [PATCH 1/1] x86: fix a bug of wrong return erorr.
Date: Wed, 24 Aug 2011 22:39:31 +0800	[thread overview]
Message-ID: <4E550D23.8020104@windriver.com> (raw)
In-Reply-To: <4E54FF43.8050102@windriver.com>

On 08/24/11 21:40, Bruce Ashfield wrote:
> On 11-08-23 10:45 PM, Liming Wang wrote:
>> __vdso_clock_gettime should fall back to call vdso_fallback_gettime
>> function
>> if no clockid is selected, not just return error.
>
> At a glance, this seems reasonable to me .. and then I
> looked a bit more. This is in fact introduced by lttng and
> the ENIVAL does look wrong. It's worth checking out the
> latest lttng to make sure that this error isn't there as
It's still in the latest lttng patch:
http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=blobdiff;f=arch/x86/vdso/vclock_gettime.c;h=7bc481508d004c4e8dd0f5cff51aeeac8bfd0766;hp=ee55754cc3c5ff378b76f2065a610b72e757f088;hb=98052998fe2aee4423dc24fccfe991b305969656;hpb=b6c4d0eaca66305984cf1ce6bc9d49a3244b412b
> well. Our 3.0 kernel won't have this bug yet, but I'll
Yes, our 3.0 kernel hasn't this bug.

> keep an eye out for this during any lttng work.
>
> I'll merge this into the 2.6.37 tree shortly.
Please replace subject "erorr" with "error" for my fault.

Liming Wang
>
> Cheers,
>
> Bruce
>
>>
>> Signed-off-by: Liming Wang<liming.wang@windriver.com>
>> ---
>> arch/x86/vdso/vclock_gettime.c | 2 --
>> 1 files changed, 0 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/vdso/vclock_gettime.c
>> b/arch/x86/vdso/vclock_gettime.c
>> index 7bc4815..2365a5b 100644
>> --- a/arch/x86/vdso/vclock_gettime.c
>> +++ b/arch/x86/vdso/vclock_gettime.c
>> @@ -173,8 +173,6 @@ notrace int __vdso_clock_gettime(clockid_t clock,
>> struct timespec *ts)
>> return do_trace_clock(ts);
>> case CLOCK_TRACE_FREQ:
>> return do_trace_clock_freq(ts);
>> - default:
>> - return -EINVAL;
>> }
>> return vdso_fallback_gettime(clock, ts);
>> }
>
>



      reply	other threads:[~2011-08-24 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  2:45 [PATCH 0/1] x86: fix a bug of wrong return erorr Liming Wang
2011-08-24  2:45 ` [PATCH 1/1] " Liming Wang
2011-08-24 13:40   ` Bruce Ashfield
2011-08-24 14:39     ` Wang Liming [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=4E550D23.8020104@windriver.com \
    --to=liming.wang@windriver.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=yocto@yoctoproject.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.