From: Greg Kroah-Hartman Date: Mon, 26 Feb 2007 23:29:05 +0000 (-0800) Subject: fixed up the From: line on some patches X-Git-Tag: v2.6.19.6~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f55a5fe9348e5e32e96cca2cce10b5290ed4a7d5;p=thirdparty%2Fkernel%2Fstable-queue.git fixed up the From: line on some patches --- diff --git a/queue-2.6.19/backport-of-psmouse-suspend-shutdown-cleanups.patch b/queue-2.6.19/backport-of-psmouse-suspend-shutdown-cleanups.patch index 35810508306..6d3d8e837bb 100644 --- a/queue-2.6.19/backport-of-psmouse-suspend-shutdown-cleanups.patch +++ b/queue-2.6.19/backport-of-psmouse-suspend-shutdown-cleanups.patch @@ -5,6 +5,7 @@ Subject: Backport of psmouse suspend/shutdown cleanups Cc: Dmitry Torokhov Message-ID: <1172148760.10619.197.camel@d36.suse.de> +From: Thomas Renninger This patch works back to 2.6.17 (earlier kernels seem to need up/down operations on mutex/semaphore). diff --git a/queue-2.6.19/fix-memory-corruption-from-misinterpreted-bad_inode_ops-return-values.patch b/queue-2.6.19/fix-memory-corruption-from-misinterpreted-bad_inode_ops-return-values.patch index e8719a854a9..66103f06c5c 100644 --- a/queue-2.6.19/fix-memory-corruption-from-misinterpreted-bad_inode_ops-return-values.patch +++ b/queue-2.6.19/fix-memory-corruption-from-misinterpreted-bad_inode_ops-return-values.patch @@ -6,6 +6,8 @@ To: Greg KH Cc: Chuck Ebbert Message-ID: <45DDC02F.2030002@redhat.com> +From: Eric Sandeen + CVE-2006-5753 is for a case where an inode can be marked bad, switching the ops to bad_inode_ops, which are all connected as: diff --git a/queue-2.6.19/fix-umask-when-noacl-kernel-meets-extn-tuned-for-acls.patch b/queue-2.6.19/fix-umask-when-noacl-kernel-meets-extn-tuned-for-acls.patch index 87c9a0de629..4c81be4efda 100644 --- a/queue-2.6.19/fix-umask-when-noacl-kernel-meets-extn-tuned-for-acls.patch +++ b/queue-2.6.19/fix-umask-when-noacl-kernel-meets-extn-tuned-for-acls.patch @@ -6,6 +6,7 @@ To: Greg KH Cc: Chris Wright , Tigran Aivazian , Andreas Gruenbacher Message-ID: +From: Hugh Dickins Fix insecure default behaviour reported by Tigran Aivazian: if an ext2 or ext3 or ext4 filesystem is tuned to mount with "acl", but mounted by