[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48D30335.1070908@garzik.org>
Date: Thu, 18 Sep 2008 21:41:09 -0400
From: Jeff Garzik <jeff@...zik.org>
To: akpm@...ux-foundation.org
CC: netdev@...r.kernel.org, chrisl@...are.com, arvidjaar@...l.ru,
bruce.w.allan@...el.com, jeffrey.t.kirsher@...el.com,
jesse.brandeburg@...el.com, john.ronciak@...el.com,
peter.p.waskiewicz.jr@...el.com, pratap@...are.com, zach@...are.com
Subject: Re: [patch for 2.6.27? 3/6] e1000: prevent corruption of EEPROM/NVM
akpm@...ux-foundation.org wrote:
> From: Christopher Li <chrisl@...are.com>
>
> 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.
>
> [akpm@...ux-foundation.org: use DEFINE_SPINLOCK to avoid confusing lockdep]
> Signed-off-by: Christopher Li <chrisl@...are.com>
> Reported-by: Andrey Borzenkov <arvidjaar@...l.ru>
> Cc: Zach Amsden <zach@...are.com>
> Cc: Pratap Subrahmanyam <pratap@...are.com>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> Cc: Jesse Brandeburg <jesse.brandeburg@...el.com>
> Cc: Bruce Allan <bruce.w.allan@...el.com>
> Cc: PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>
> Cc: John Ronciak <john.ronciak@...el.com>
> Cc: Jeff Garzik <jeff@...zik.org>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> ---
>
> 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.
--
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