Linux 2.4.35.5

From: Willy Tarreau
Date: Sun Dec 16 2007 - 18:48:18 EST



I've just released Linux 2.4.35.5.

It simply gets up to date with 2.4.36-rc1. One important thing to
keep in mind is that I explicitly disabled the possibility to build
with GCC 4.2 because several users (me included) encountered silent
mis-compilations.

So if you think that you have built your last version with 4.2, just
check if you can build this one. If you can, then you use a correct,
older GCC version. Otherwise, you'll have to install an old one for
the moment. Anyway, this update contains enough fixes for minor to
medium vulnerabilities to justify an upgrade.

Depending on the activity in the security area during the following
weeks, this version might be the last 2.4.35.X. So if you have not
yet tried 2.4.36-rc, it is time to do so.

The patch and changelog will appear soon at the following locations:
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/patch-2.4.35.5.bz2
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.35.5

Git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.35.y.git
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.35.y.git

Git repository through the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-v2.4.35.y.git

Regards,
Willy

---

Summary of changes from v2.4.35.4 to v2.4.35.5
============================================

Jonas Danielsson (1):
net/ipv4/arp.c: Fix arp reply when sender ip 0

Krzysztof Strasburger (1):
fix arch/i386/config.in to be able to boot on 386

Pete Zaitcev (1):
usb: Move linux-usb-devel

Willy Tarreau (7):
GCC >= 4.2 miscompiles the kernel
fix build of ia32entry.S on x86_64
vfs: coredumping fix
isdn: avoid copying overly-long strings
isdn: fix isdn_ioctl memory overrun vulnerability
prevent SIGCONT from waking up a PTRACED process (CVE-2007-4774)
Change VERSION to 2.4.35.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/