From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.34.5
Date: Wed, 6 Jun 2007 20:53:47 +0000 [thread overview]
Message-ID: <20070606205347.GA24188@hera.kernel.org> (raw)
Hi all,
I've just released Linux 2.4.34.5, with extracts from 2.4.35-pre5.
The most important one is the fix for the regression I introduced
while fixing CVE-2007-1353 (bluetooth). Basically, I turned a memory
leak bug into a memory corruption bug. Two minor bluetooth fixes have
all been backported from 2.6 too.
The other (less) important fix solves the problem of ide-disk.o causing
oopses after insmod, it was caused by init_idle() being erroneously
marked __init.
Last, a minor LVM fix from the RHEL3 kernel to correctly count extents
in case of errors during snapshot allocation.
Regards,
Willy
The patch and changelog will appear soon at the following locations:
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/patch-2.4.34.5.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.34.5
Git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.34.y.git
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.34.y.git
Git repository through the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-v2.4.34.y.git
Summary of changes from v2.4.34.4 to v2.4.34.5
============================================
Willy Tarreau (6):
do not mark init_idle() __init
Bluetooth: correct fix for CVE-2007-1353
[BACKPORT] Bluetooth: Fix NULL pointer dereference in HCI line discipline
[BACKPORT] Bluetooth: Fix unintentional fall-through in HCI line discipline
lvm: do not update extent count if snapshot allocation fails
Change VERSION to 2.4.34.5
reply other threads:[~2007-06-06 20:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070606205347.GA24188@hera.kernel.org \
--to=wtarreau@hera.kernel.org \
--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