Messages in this thread | | | From | "Allan, Bruce W" <> | Date | Tue, 30 Sep 2008 08:47:24 -0700 | Subject | RE: [RFC PATCH 11/12] e1000e: write protect ICHx NVM to prevent malicious write/erase |
| |
Yeah, we can do that. I need to amend the patch a bit to prevent the protected range lock from being lifted unintentionally and will add some debug statements if/when any write/erase cycles fail.
-----Original Message----- From: Jiri Kosina [mailto:jkosina@suse.cz] Sent: Tuesday, September 30, 2008 5:41 AM To: Brandeburg, Jesse Cc: linux-kernel@vger.kernel.org; linux-netdev@vger.kernel.org; kkeil@suse.de; agospoda@redhat.com; arjan@linux.intel.com; Graham, David; Allan, Bruce W; Ronciak, John; Thomas Gleixner; chris.jones@canonical.com; tim.gardner@intel.com; airlied@gmail.com; Allan, Bruce W Subject: Re: [RFC PATCH 11/12] e1000e: write protect ICHx NVM to prevent malicious write/erase
On Mon, 29 Sep 2008, Jesse Brandeburg wrote:
> Set the hardware to ignore all write/erase cycles to the GbE region in > the ICHx NVM. This feature can be disabled by the WriteProtectNVM module > parameter (enabled by default) though that is not recommended. > > Signed-off-by: Bruce Allan <bruce.w.allan@intel.com> > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
I guess there is no chance to have kernel somehow notified when write/erase cycle is unsuccessfully tried, is it? This way, it would also make chasing the root cause easier.
Thanks,
-- Jiri Kosina SUSE Labs
| |