lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 02 Oct 2008 16:33:14 -0700 From: Jesse Brandeburg <jesse.brandeburg@...el.com> To: torvalds@...ux-foundation.org Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org, tglx@...utronix.de, arjan@...ux.intel.com, airlied@...il.com, davem@...emloft.net, jeff@...zik.org Subject: [PATCH 2.6.27-rc8 0/6] e1000e mutex protection This series of patches fixes several bugs found by putting a mutex inside e1000_acquire_swfw_flag, and then the patch from Thomas actually adds this mutex to help find any further bugs. Like Jesse Barnes said, "totally up to you (obviously) whether we stuff this into 2.6.27 or hold on it until 2.6.28." Linus, since you mentioned this exact same issue that Thomas (and Dave Airlie) spotted I figured I should just send these. Testing will continue over the next couple of days and I'll let you know immediately if we find something. The patches are pretty straight forward and each one fixed a separate bug we found using the mutex patch. It is possible that these fix the actual corruption issue but we haven't verified that yet. --- Jesse Brandeburg (5): e1000e: update version from k4 to k6 e1000e: drop stats lock e1000e: remove phy read from inside spinlock e1000e: do not ever sleep in interrupt context e1000e: reset swflag after resetting hardware Thomas Gleixner (1): e1000e: debug contention on NVM SWFLAG drivers/net/e1000e/e1000.h | 3 +- drivers/net/e1000e/ethtool.c | 6 +++- drivers/net/e1000e/ich8lan.c | 20 +++++++++++++ drivers/net/e1000e/netdev.c | 64 +++++++++++++++++++----------------------- 4 files changed, 56 insertions(+), 37 deletions(-) -- Jesse Brandeburg -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists