[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081002001830.5951.3123.stgit@jbrandeb-bw.jf.intel.com>
Date: Wed, 01 Oct 2008 17:18:30 -0700
From: Jesse Brandeburg <jesse.brandeburg@...el.com>
To: torvalds@...ux-foundation.org, jeff@...zik.org, davem@...emloft.net
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
arjan@...ux.intel.com
Subject: [PATCH 2.6.27-rc8 0/1] e1000e nvm fix
Please apply to 2.6.27
This is related to regression bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=11382
This patch is meant to prevent all future corruptions of the
e1000e NVM (non volatile memory) after the driver is loaded. The
registers stay locked until the machine is power cycled.
This should allow us to move forward with debugging without
allowing any other bad element or the e1000e driver, to write to
the NVM area unexpectedly.
Currently we (Intel Ethernet) are reproducing the issue on
multiple machines in house, we are working on the issue with the
other core Linux teams here at Intel and within the community. No
resolution yet but we are much closer now.
Later we will post patches to help users who have had this
problem restore their eeprom from either a saved image from
ethtool -e or from another identical system.
There is a set of patches to help clean up the driver's use of
the hardware/software semaphore, but those are un-necessary to be
immediately applied once we're locking the NVM. We will push
those for inclusion within the merge window for 2.6.28.
---
Bruce Allan (1):
e1000e: write protect ICHx NVM to prevent malicious write/erase
drivers/net/e1000e/e1000.h | 2 +
drivers/net/e1000e/ethtool.c | 3 ++
drivers/net/e1000e/ich8lan.c | 58 ++++++++++++++++++++++++++++++++++++++++++
drivers/net/e1000e/netdev.c | 10 +++++--
drivers/net/e1000e/param.c | 30 ++++++++++++++++++++++
5 files changed, 100 insertions(+), 3 deletions(-)
--
Jesse Brandeburg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists