From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jiri Kosina <jkosina@suse.cz>,
Michael Gilbert <michael.s.gilbert@gmail.com>,
Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: CVE-2009-2584
Date: Thu, 5 Nov 2009 10:19:43 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.01.0911051018080.31845@localhost.localdomain> (raw)
In-Reply-To: <200911051847.36103.mb@bu3sch.de>
On Thu, 5 Nov 2009, Michael Buesch wrote:
>
> Looks OK to me. I can't test it however, as I don't own the hardware.
Heh. Even the people who wanted to write exploit examples had the same
small problem. I doubt it really matters for anybody.
I'm committing it, just because I don't think it can really be any worse
than the status quo. But I'll happily take further patches, especially
from anybody who actually has access to the hardware.
Linus
next prev parent reply other threads:[~2009-11-05 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 22:05 CVE-2009-2584 Michael Gilbert
2009-11-04 22:08 ` CVE-2009-2584 Justin P. Mattock
2009-11-04 22:21 ` CVE-2009-2584 Michael Gilbert
2009-11-04 22:49 ` CVE-2009-2584 Justin P. Mattock
2009-11-05 15:27 ` CVE-2009-2584 Jiri Kosina
2009-11-05 16:32 ` CVE-2009-2584 Linus Torvalds
2009-11-05 17:38 ` CVE-2009-2584 Linus Torvalds
2009-11-05 17:47 ` CVE-2009-2584 Linus Torvalds
2009-11-05 17:47 ` CVE-2009-2584 Michael Buesch
2009-11-05 18:16 ` CVE-2009-2584 Jack Steiner
2009-11-05 18:22 ` CVE-2009-2584 Linus Torvalds
2009-11-05 18:41 ` CVE-2009-2584 Jack Steiner
2009-11-05 18:19 ` Linus Torvalds [this message]
2009-11-05 17:56 ` CVE-2009-2584 Roland Dreier
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=alpine.LFD.2.01.0911051018080.31845@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=michael.s.gilbert@gmail.com \
--cc=stable@kernel.org \
--cc=steiner@sgi.com \
/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
Powered by JetHome