From: Chris Wright <chrisw@sous-sol.org>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: Chris Wright <chrisw@sous-sol.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.16
Date: Thu, 11 May 2006 10:33:12 -0700 [thread overview]
Message-ID: <20060511173312.GI25010@moss.sous-sol.org> (raw)
In-Reply-To: <296295514.20060511123419@dns.toxicfilms.tv>
* Maciej Soltysiak (solt2@dns.toxicfilms.tv) wrote:
> But this one looks important, something that every kernel build
> has in its code path, however I am unable to say if I need it badly
> or maybe not.
The patch fixes a possible user-triggerable system lockup or memory leak.
In both cases it's a local DoS.
BTW, the CVE folks have decided to track this as two separate issues:
CVE-2006-1860 - the system lockup
CVE-2006-1859 - the memory leak
> Could we have a word or two under each patchlet that would qualify them
> somehow?
> Like:
> "Important, not required for all, apply if using SCTP"
> "Important, required for all, may *do bad things*, apply ASAP"
> "Critical, required for all, surely will *do bad things*, apply ASAP"
Assigning any official severity is a bit of a slippery slope, but
making sure it's clear what type of issue (i.e. local DoS in this case)
is very reasonable.
thanks,
-chris
next prev parent reply other threads:[~2006-05-11 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 2:25 Chris Wright
2006-05-11 2:29 ` Chris Wright
2006-05-11 10:34 ` Maciej Soltysiak
2006-05-11 11:07 ` Nick Warne
2006-05-11 16:50 ` Daniel Barkalow
2006-05-11 17:33 ` Chris Wright [this message]
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-05-13 15:35 ` Linux 2.6.16.16 Ingo Oeser
2006-05-13 15:56 ` Adrian Bunk
2006-05-13 17:29 ` Nick Warne
2006-05-14 3:59 ` Greg KH
2006-05-14 5:17 ` Willy Tarreau
2006-05-15 17:57 ` Chris Wright
2006-05-14 7:46 ` Maciej Soltysiak
2006-05-15 16:30 ` Greg KH
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=20060511173312.GI25010@moss.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
/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