[kernel-sec-discuss] r5432 - active retired

Salvatore Bonaccorso carnil at moszumanska.debian.org
Sun Jul 23 09:12:02 UTC 2017


Author: carnil
Date: 2017-07-23 09:12:02 +0000 (Sun, 23 Jul 2017)
New Revision: 5432

Added:
   active/CVE-2015-8952
Removed:
   retired/CVE-2015-8952
Log:
Move CVE-2015-8952 back to active, since likely to backport to 3.2 and 3.16 the mount option

Copied: active/CVE-2015-8952 (from rev 5431, retired/CVE-2015-8952)
===================================================================
--- active/CVE-2015-8952	                        (rev 0)
+++ active/CVE-2015-8952	2017-07-23 09:12:02 UTC (rev 5432)
@@ -0,0 +1,22 @@
+Description:
+References:
+ https://lwn.net/Articles/668718/
+ https://bugzilla.redhat.com/show_bug.cgi?id=1360968
+ https://bugzilla.kernel.org/show_bug.cgi?id=107301
+Notes:
+ bwh> The upstream fix (rewrite of mbcache) is too intrusive to backport.
+ bwh> We will mitigate this with cond_resched() as suggested in comment 1
+ bwh> on the bz.k.o bug report.  I didn't want to add the no_mbcache mount
+ bwh> option as in comment 12 because it's a uAPI extension, but it has
+ bwh> now been added upstream (commit cdb7ee4c6327) so I think it would be
+ bwh> reasonable to add it to supported stable releases.
+ bwh> The problem seems to have been introduced (or exacerbated) by commit
+ bwh> 1f3e55fe02d1 in 3.15, which added a retry loop in mb_cache_entry_alloc().
+Bugs:
+upstream: released (4.6-rc1) [f9a61eb4e2471c56a63cd804c7474128138c38ac, 82939d7999dfc1f1998c4b1c12e2f19edbdff272, be0726d33cb8f411945884664924bed3cb8c70ee]
+4.9-upstream-stable: N/A "Fixed before branch point"
+3.16-upstream-stable: ignored "Too intrusive to backport"
+3.2-upstream-stable: ignored "Too intrusive to backport, and seems to be minor issue"
+sid: released (4.6.1-1)
+3.16-jessie-security: ignored "Too intrusive to backport, but will be mitigated"
+3.2-wheezy-security: ignored "Too intrusive to backport, and seems to be minor issue"

Deleted: retired/CVE-2015-8952
===================================================================
--- retired/CVE-2015-8952	2017-07-22 23:38:22 UTC (rev 5431)
+++ retired/CVE-2015-8952	2017-07-23 09:12:02 UTC (rev 5432)
@@ -1,22 +0,0 @@
-Description:
-References:
- https://lwn.net/Articles/668718/
- https://bugzilla.redhat.com/show_bug.cgi?id=1360968
- https://bugzilla.kernel.org/show_bug.cgi?id=107301
-Notes:
- bwh> The upstream fix (rewrite of mbcache) is too intrusive to backport.
- bwh> We will mitigate this with cond_resched() as suggested in comment 1
- bwh> on the bz.k.o bug report.  I didn't want to add the no_mbcache mount
- bwh> option as in comment 12 because it's a uAPI extension, but it has
- bwh> now been added upstream (commit cdb7ee4c6327) so I think it would be
- bwh> reasonable to add it to supported stable releases.
- bwh> The problem seems to have been introduced (or exacerbated) by commit
- bwh> 1f3e55fe02d1 in 3.15, which added a retry loop in mb_cache_entry_alloc().
-Bugs:
-upstream: released (4.6-rc1) [f9a61eb4e2471c56a63cd804c7474128138c38ac, 82939d7999dfc1f1998c4b1c12e2f19edbdff272, be0726d33cb8f411945884664924bed3cb8c70ee]
-4.9-upstream-stable: N/A "Fixed before branch point"
-3.16-upstream-stable: ignored "Too intrusive to backport"
-3.2-upstream-stable: ignored "Too intrusive to backport, and seems to be minor issue"
-sid: released (4.6.1-1)
-3.16-jessie-security: ignored "Too intrusive to backport, but will be mitigated"
-3.2-wheezy-security: ignored "Too intrusive to backport, and seems to be minor issue"




More information about the kernel-sec-discuss mailing list