From: Chuck Ebbert <76306.1226@compuserve.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.37
Date: Sun, 7 Jan 2007 03:35:21 -0500 [thread overview]
Message-ID: <200701070337_MC3-1-D79B-2928@compuserve.com> (raw)
In-Reply-To: <20070104222517.GL20714@stusta.de>
On Thu, 4 Jan 2007 23:25:17 +0100, Adrian Bunk wrote:
> There's already a CVE number for
> "i386: save/restore eflags in context switch".
>
> Are there also CVE numbers for the equivalent x86_64 patch and
> "x86_64: fix ia32 syscall count"?
Sorry, my Web access is broken for now so I can't check, but I believe
that CVE number is for a different, older problem.
So AFAIK there are no CVE numbers for anything I sent (but there
probably should be.) Generic Linux kernel developers don't have
a CVE representative, so we depend on vendors to assign numbers
and sometimes they don't.
--
"That's the problem with non-representational art:
you can't tell which part offends you."
--Stephen Colbert
next reply other threads:[~2007-01-07 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 8:35 Chuck Ebbert [this message]
2007-01-08 21:49 ` Linux 2.6.16.37 Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-12-31 22:05 Chuck Ebbert
2007-01-04 22:25 ` Adrian Bunk
2006-12-28 13:53 Adrian Bunk
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=200701070337_MC3-1-D79B-2928@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox