From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: linux-kernel@vger.kernel.org
Cc: Willy Tarreau <willy@w.ods.org>
Subject: Linux 2.4.33-pre2
Date: Tue, 21 Feb 2006 15:48:44 -0600 [thread overview]
Message-ID: <20060221214844.GA22561@dmt.cnet> (raw)
Hi,
Here goes the second -pre of v2.4.33, containing a small number of
changes.
Most notably three security corrections, and an overflow fix for
machines with large amounts of memory and inodes (which would cause the
system's logic to reclaim inodes with highmem pages attached to fail).
Please refer to the changelog for full details...
Summary of changes from v2.4.33-pre1 to v2.4.33-pre2
============================================
Adrian Bunk:
document that gcc 4 is not supported
dann frazier:
proc_pid_cmdline() race fix (CAN-2004-1058)
David S. Miller:
[SPARC]: Fix compile failures in math-emu.
Guennadi Liakhovetski:
usb-uhci.c: wrong sign comparison in status check
Horms:
[PATCH, 2.4] wan sdla: fix probable security hole
orinoco: CVE-2005-3180: Information leakage due to incorrect padding
Jacek Lipkowski:
make 2.4.32 work on i486 again
Jesse Brandeburg:
e1000: fix BUG reported due to calling msec_delay in irq context
Marcelo Tosatti:
Alpha: fix recursive inlining failure in pci_iommu.c
Merge http://w.ods.org/kernel/2.4/linux-2.4-upstream
Change VERSION to 2.4.33-pre2
ODonnell, Michael:
PATCH: hash-table corruption in bond_alb.c
Pete Zaitcev:
usbserial: using int for CPU flags is incorrect on x86_64
Rik van Riel:
fix overflow in inode.c
Steven J. Hathaway:
SAMSUNG CD-ROM SC-140 fails on DMA
Vincent Fortier:
Documentation error 2.4.x aic7xxx
Willy Tarreau:
Merge branch 'master' of /data/projets/git/linux/linux-2.4
Merge branch 'master' of /data/projets/git/linux/linux-2.4
next reply other threads:[~2006-02-21 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:48 Marcelo Tosatti [this message]
2006-02-21 21:00 ` Linux 2.4.33-pre2 Willy Tarreau
2006-02-25 9:53 ` Geert Uytterhoeven
2006-02-25 20:55 ` Marcelo Tosatti
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=20060221214844.GA22561@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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