From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.32-pre1
Date: Mon, 4 Jul 2005 09:47:53 -0300 [thread overview]
Message-ID: <20050704124753.GA23706@logos.cnet> (raw)
Hi,
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 <ak@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 <davem@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 <hjl@lucon.org>:
newer i386/x86_64 assemblers prohibit instructions for moving between a seg register and a 32bit location
Marcel Holtmann <marcel@holtmann.org>:
Fix" introduced in 2.4.27pre2 for bluetooth hci_usb race causes kernel hang
Marcelo <marcelo@xeon.cnet>:
Change VERSION to 2.4.32-pre1
NeilBrown <neilb@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 <zaitcev@redhat.com>:
USB 2.4.31: ftdi_sio fixes
Ralf Baechle <ralf@linux-mips.org>:
update netdev address
reply other threads:[~2005-07-04 17:45 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=20050704124753.GA23706@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--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