From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PATCH] Fixes in the -stable tree, but not in mainline
Date: Mon, 17 Apr 2006 14:29:46 -0700 [thread overview]
Message-ID: <20060417212946.GA3118@kroah.com> (raw)
Here are 5 patches that are in the -stable tree, yet not currently fixed
in your mainline tree. One of them is a security fix, so it probably
would be a good idea to get it into there :)
Please pull from:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/stable-2.6.git/
or from:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/stable-2.6.git/
if it isn't synced up yet.
The full patch series will sent to the linux-kernel mailing list, if
anyone wants to see them.
thanks,
greg k-h
drivers/block/cciss.c | 96 ++++++++++++++++++++++----------------------
drivers/usb/storage/Kconfig | 3 -
fs/ext3/resize.c | 1
fs/partitions/check.c | 5 ++
ipc/shm.c | 2
5 files changed, 59 insertions(+), 48 deletions(-)
---------------
Ananiev, Leonid I:
ext3: Fix missed mutex unlock
Hugh Dickins:
shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524)
Mike Miller:
cciss: bug fix for crash when running hpacucli
Randy Dunlap:
isd200: limit to BLK_DEV_IDE
Stephen Rothwell:
Fix block device symlink name
next reply other threads:[~2006-04-17 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 21:29 Greg KH [this message]
2006-04-17 21:33 ` [PATCH 1/5] isd200: limit to BLK_DEV_IDE Greg KH
2006-04-17 21:33 ` [PATCH 2/5] Fix block device symlink name Greg KH
2006-04-17 21:33 ` [PATCH 3/5] ext3: Fix missed mutex unlock Greg KH
2006-04-17 21:33 ` [PATCH 4/5] cciss: bug fix for crash when running hpacucli Greg KH
2006-04-17 21:33 ` [PATCH 5/5] shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524) Greg KH
2006-04-18 16:06 ` [GIT PATCH] Fixes in the -stable tree, but not in mainline Theodore Ts'o
2006-04-18 17:42 ` Greg KH
2006-04-18 20:39 ` Andrew Morton
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=20060417212946.GA3118@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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