From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
dang@gentoo.org, stable@kernel.org
Subject: Re: [Bugme-new] [Bug 8479] New: gettimeofday returning 1000000 in tv_usec on core2duo
Date: Tue, 15 May 2007 09:22:47 +0200 [thread overview]
Message-ID: <200705150922.47702.ak@suse.de> (raw)
In-Reply-To: <20070514232301.69e27bbe.akpm@linux-foundation.org>
> >
> > I remember I already hit this and corrected it
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdi
> >ff;f=arch/x86_64/kernel/vsyscall.c;h=dc32cef961950915fbaa185e36ab802d5f7ce
> >a3b;hp=ba330f87067996a17495f7d03466d646c718b52c;hb=c8118c6c07f2edfd697aaa0
> >b93e08c3b65a5a675;hpb=272a3713bb9e302e0455c894c41180a482d2c8a3
>
> Oh, OK.
>
> > Maybe a stable push is necessary ?
>
> yup. Please always think of -stable when preparing fixes. I'm sure many
> useful fixes are slipping past simply because those who _are_ looking out
> for backportable fixes are missing things.
>
> Greg, Chris: please consider c8118c6c07f2edfd697aaa0b93e08c3b65a5a675
> for -stable, if it isn't already there.
The full patch is overkill because 99% of it is an totally unrelated
optimization. Only the > -> >= change should be backported
-Andi
next prev parent reply other threads:[~2007-05-15 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705150417.l4F4HlvS013354@fire-2.osdl.org>
2007-05-15 5:09 ` [Bugme-new] [Bug 8479] New: gettimeofday returning 1000000 in tv_usec on core2duo Andrew Morton
2007-05-15 6:06 ` Eric Dumazet
2007-05-15 6:23 ` Andrew Morton
2007-05-15 7:22 ` Andi Kleen [this message]
2007-05-15 8:17 ` Eric Dumazet
2007-05-15 14:55 ` Daniel Gryniewicz
2007-05-19 14:30 ` Bill Davidsen
2007-05-19 17:59 ` Eric Dumazet
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=200705150922.47702.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dada1@cosmosbay.com \
--cc=dang@gentoo.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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