From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, discuss@x86-64.org,
Steven James <pyro@linuxlabs.com>, Jeff Dike <jdike@addtoit.com>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: Re: [uml-devel] [discuss] [RFC] [PATCH] Double syscall exit traces on x86_64
Date: Fri, 2 Jun 2006 11:13:35 -0400 [thread overview]
Message-ID: <20060602151335.GA4708@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200606012107.34676.blaisorblade@yahoo.it>
On Thu, Jun 01, 2006 at 09:07:33PM +0200, Blaisorblade wrote:
> Sorry for the question, but has this been sent to -stable (since it's a
> -stable regression, it should be)? To 2.6.17 -git?
It's in current git.
I'm having a hard time telling when the bug was introduced. The git web
interface seems to be telling me that the double notification was around
since last year, which I don't believe, since I've run much more
recent x86_64 kernels. If the bug existed before 2.6.16, then it's
fine -stable fodder.
> And have you tested it (somebody should have, but it's not sure)?
Yes, it's been continuously and happily running UML since Andi sent me
his patch.
Jeff
next prev parent reply other threads:[~2006-06-02 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:24 [RFC] [PATCH] Double syscall exit traces on x86_64 Jeff Dike
2006-05-26 10:36 ` [discuss] " Andi Kleen
2006-05-26 14:13 ` Jeff Dike
2006-06-01 19:07 ` [uml-devel] " Blaisorblade
2006-06-02 15:13 ` Jeff Dike [this message]
2006-06-02 15:38 ` [uml-devel] " Steven James
2006-06-02 17:16 ` Blaisorblade
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=20060602151335.GA4708@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=ak@suse.de \
--cc=blaisorblade@yahoo.it \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pyro@linuxlabs.com \
--cc=roland@redhat.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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