From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, stable@kernel.org
Cc: torvalds@osdl.org, akpm@osdl.org
Subject: Linux 2.6.13.4
Date: Mon, 10 Oct 2005 12:55:42 -0700 [thread overview]
Message-ID: <20051010195542.GA12763@kroah.com> (raw)
We (the -stable team) are announcing the release of the 2.6.13.3 kernel.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the patch between
2.6.13.3 and 2.6.13.4, as it is small enough to do so.
The updated 2.6.13.y git tree can be found at:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/linux-2.6.13.y.git
and can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/
thanks,
greg k-h
--------
Makefile | 2 +-
arch/sparc64/kernel/entry.S | 39 +++++++++++++++++++++------------------
arch/sparc64/kernel/rtrap.S | 7 ++++---
arch/sparc64/lib/VISsave.S | 8 +++++---
drivers/char/drm/drm_stub.c | 2 +-
drivers/ieee1394/sbp2.c | 38 +++++++++++++++++++++++++++++++++++---
drivers/net/wireless/orinoco.c | 14 +++++++++-----
fs/namei.c | 6 +++---
net/ipv4/tcp_bic.c | 2 +-
security/keys/request_key_auth.c | 1 +
10 files changed, 81 insertions(+), 38 deletions(-)
Summary of changes from v2.6.13.3 to v2.6.13.4
============================================
Dave Jones:
Fix drm 'debug' sysfs permissions
David Howells:
key: plug request_key_auth memleak (CAN-2005-3119)
David S. Miller:
Fix userland FPU state corruption.
Greg Kroah-Hartman:
Linux 2.6.13.4
Linus Torvalds:
Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
Pavel Roskin:
orinoco: Information leakage due to incorrect padding
Stefan Richter:
ieee1394/sbp2: fixes for hot-unplug and module unloading
Stephen Hemminger:
BIC coding bug in Linux 2.6.13
next reply other threads:[~2005-10-10 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 19:55 Greg KH [this message]
2005-10-10 19:56 ` Greg KH
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=20051010195542.GA12763@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®