Subject: Re: [patch for 2.6.27? 3/6] e1000: prevent corruption of EEPROM/NVM

From: Jeff Garzik <[email-masked]>
Date: Thu, 18 Sep 2008 21:41:09 -0400

[email-masked] wrote:
> From: Christopher Li <[email-masked]> 
> 
> Andrey reports e1000 corruption, and that a patch in vmware's ESX fixed
> it.
> 
> The EEPROM corruption is triggered by concurrent access of the EEPROM
> read/write. Putting a lock around it solve the problem.
> 
> [[email-masked]: use DEFINE_SPINLOCK to avoid confusing lockdep]
> Signed-off-by: Christopher Li <[email-masked]>
> Reported-by: Andrey Borzenkov <[email-masked]>
> Cc: Zach Amsden <[email-masked]>
> Cc: Pratap Subrahmanyam <[email-masked]>
> Cc: Jeff Kirsher <[email-masked]>
> Cc: Jesse Brandeburg <[email-masked]>
> Cc: Bruce Allan <[email-masked]>
> Cc: PJ Waskiewicz <[email-masked]>
> Cc: John Ronciak <[email-masked]>
> Cc: Jeff Garzik <[email-masked]>
> Signed-off-by: Andrew Morton <[email-masked]>
> ---
> 
>  drivers/net/e1000/e1000_hw.c |   23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)

No further reply from Intel to my ping, and this regression needs to be 
addressed, so, applied.