All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org, lkml@lpbproductions.com
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	jbeulich@novell.com, richard.brunner@amd.com
Subject: Re: [discuss] Re: [PATCH] [1/2] i386/x86-64: Fix x87 information leak between  processes
Date: Thu, 20 Apr 2006 08:39:00 +0200	[thread overview]
Message-ID: <200604200839.00606.ak@suse.de> (raw)
In-Reply-To: <200604192328.39429.lkml@lpbproductions.com>

On Thursday 20 April 2006 08:28, Matt Heler wrote:
> Patch says 1/2 . Is there another patch that comes with this ? Or is vger 
> lagging again ? 

The other patch was a unrelated x86-64 only patch which I normally
not cc to linux-kernel, but only to discuss@x86-64.org. You 
can check it out in the archives.

-Andi

      reply	other threads:[~2006-04-20  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20  0:36 [PATCH] [1/2] i386/x86-64: Fix x87 information leak between processes Andi Kleen
2006-04-20  6:28 ` Matt Heler
2006-04-20  6:39   ` Andi Kleen [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=200604200839.00606.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lpbproductions.com \
    --cc=richard.brunner@amd.com \
    --cc=torvalds@osdl.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.