From: Willy Tarreau <w@1wt.eu>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Linux 2.6.32.59
Date: Sat, 17 Mar 2012 14:09:53 +0100 [thread overview]
Message-ID: <20120317130953.GA16926@1wt.eu> (raw)
I've just released Linux 2.6.32.59.
The patch and changelog will appear soon at the following locations:
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/longterm/2.6.32/
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/longterm/2.6.32/patch-2.6.32.59.bz2
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/longterm/2.6.32/patch-2.6.32.59.xz
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/longterm/2.6.32/patch-2.6.32.59.gz
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/longterm/2.6.32/ChangeLog-2.6.32.59
The updated 2.6.32.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-2.6.32.y
http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-2.6.32.y
The tree can be browsed on the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/heads/linux-2.6.32.y
Testing status (build/boot, OK/FAIL, otherwise not tested) :
ARCH | CONFIGURATION
--------+-----------------------------------
| allmodconfig other-config
x86_64 | build:OK -
i386 | build:OK boot:OK
Thanks to all reviewers, and to Greg for the final packaging.
Willy
---------
Makefile | 2 +-
arch/ia64/Kconfig | 17 -----------------
arch/s390/Kconfig | 3 +++
arch/s390/kernel/setup.c | 1 +
block/bsg.c | 3 ++-
drivers/block/xen-blkfront.c | 4 ++--
drivers/net/usb/usbnet.c | 2 ++
drivers/watchdog/hpwdt.c | 5 +++--
fs/binfmt_elf.c | 2 +-
fs/cifs/dir.c | 20 ++++++++++++++++++--
fs/ecryptfs/crypto.c | 21 +++++++++++++++++++++
fs/ecryptfs/ecryptfs_kernel.h | 2 ++
fs/ecryptfs/file.c | 3 ++-
fs/ecryptfs/inode.c | 18 +++---------------
include/linux/backing-dev.h | 1 +
include/linux/regset.h | 10 ++++++++--
mm/backing-dev.c | 15 ++++++++++-----
mm/page-writeback.c | 1 +
18 files changed, 81 insertions(+), 49 deletions(-)
Summary of changes from 2.6.32.58 to 2.6.32.59
==============================================
Ben Hutchings (1):
IA64: Remove COMPAT_IA32 support
David Howells (1):
KEYS: Enable the compat keyctl wrapper on s390x
David Vrabel (1):
blkfront: Fix backtrace in del_gendisk
H. Peter Anvin (2):
regset: Prevent null pointer reference on readonly regsets
regset: Return -EFAULT, not -EIO, on host-side memory fault
Heiko Carstens (1):
compat: Re-add missing asm/compat.h include to fix compile breakage on s390
Jeff Layton (1):
cifs: fix dentry refcount leak when opening a FIFO on lookup
Jens Axboe (1):
writeback: fixups for !dirty_writeback_centisecs
Maxim Uvarov (1):
watchdog: hpwdt: clean up set_memory_x call for 32 bit
Sebastian Siewior (1):
net/usbnet: avoid recursive locking in usbnet_stop()
Stanislaw Gruszka (1):
bsg: fix sysfs link remove warning
Tyler Hicks (1):
eCryptfs: Handle failed metadata read in lookup
Willy Tarreau (1):
Linux 2.6.32.59
next reply other threads:[~2012-03-17 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 13:09 Willy Tarreau [this message]
2012-03-18 11:20 ` Linux 2.6.32.59 Nikola Ciprich
2012-03-18 11:59 ` Willy Tarreau
2012-03-18 13:22 ` Arnd Hannemann
2012-03-18 13:28 ` Willy Tarreau
2012-03-18 15:17 ` Greg KH
2012-03-18 16:30 ` Willy Tarreau
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=20120317130953.GA16926@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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