Effective February 22, 2024, Google Groups will no longer support new Usenet content. Posting and subscribing will be disallowed, and new content from Usenet peers will not appear. Viewing and searching of historical data will still be supported as it is done today.

Linux 2.4.32-pre1

Skip to first unread message

Marcelo Tosatti

Jul 4, 2005, 1:47:24 PM7/4/05
to linux-...@vger.kernel.org

Here goes the first -pre of v2.4.32.

It contains a small amount of fixes, most notably x86_64 security updates.

Check for canonical addresses in ptrace (CAN-2005-1762)
Fix canonical checking for segment registers in ptrace (CAN-2005-0756)
Fix buffer overflow in 32bit execve on x86-64/ia64 (CAN-2005-1768)

Summary of changes from v2.4.31 to v2.4.32-pre1

Andi Kleen <a...@suse.de>:
x86-64: Enable Nvidia timer override workaround for SMP kernels too
x86-64: Fix build with !CONFIG_SWIOTLB
x86_64: Disable exception stack for stack faults
Fix canonical checking for segment registers in ptrace
Check for canonical addresses in ptrace
Fix buffer overflow in x86-64/ia64 32bit execve

David S. Miller <da...@davemloft.net>:
[NETLINK]: Fix two socket hashing bugs.
[SPARC64]: Fix cmsg length checks in Solaris emulation layer.
[SPARC64]: Fix conflicting __bzero_noasi() prototypes.

H. J. Lu <h...@lucon.org>:
newer i386/x86_64 assemblers prohibit instructions for moving between a seg register and a 32bit location

Marcel Holtmann <mar...@holtmann.org>:
Fix" introduced in 2.4.27pre2 for bluetooth hci_usb race causes kernel hang

Marcelo <mar...@xeon.cnet>:
Change VERSION to 2.4.32-pre1

NeilBrown <ne...@cse.unsw.edu.au>:
Claim i_alloc_sem while changing file size in nfsd
Don't drop setuid on directories when ownership changed by NFSd

Pete Zaitcev <zai...@redhat.com>:
USB 2.4.31: ftdi_sio fixes

Ralf Baechle <ra...@linux-mips.org>:
update netdev address

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

Reply all
Reply to author
0 new messages