From: David Vrabel <dvrabel@cantab.net>
To: Chris Wright <chrisw@sous-sol.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Linux 2.6.15.5
Date: Thu, 02 Mar 2006 09:49:09 +0000 [thread overview]
Message-ID: <4406BF95.8060501@cantab.net> (raw)
In-Reply-To: <20060301231907.GR3883@sorel.sous-sol.org>
Chris Wright wrote:
> We (the -stable team) are announcing the release of the 2.6.15.5
> kernel.
>
> [...]
>
> Alexey Kuznetsov: Fix a severe bug
Can we have more descriptive patch summaries in future? At least
include the subsystem!
Here's the description I dug out of the web interface to git:
"netlink overrun was broken while improvement of netlink. Destination
socket is used in the place where it was meant to be source socket, so
that now overrun is never sent to user netlink sockets, when it should
be, and it even can be set on kernel socket, which results in complete
deadlock of rtnetlink."
David Vrabel
next prev parent reply other threads:[~2006-03-02 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 23:19 Linux 2.6.15.5 Chris Wright
2006-03-01 23:20 ` Chris Wright
2006-03-02 8:52 ` Ralf Hildebrandt
2006-03-02 9:49 ` David Vrabel [this message]
2006-03-02 19:04 ` Chris Wright
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=4406BF95.8060501@cantab.net \
--to=dvrabel@cantab.net \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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