[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48BEFAC1.1030303@intel.com>
Date: Wed, 03 Sep 2008 13:59:45 -0700
From: "Kok, Auke" <auke-jan.h.kok@...el.com>
To: akpm@...ux-foundation.org
CC: jeff@...zik.org, 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? 4/4] e1000e: prevent corruption of EEPROM/NVM
akpm@...ux-foundation.org wrote:
> From: Christopher Li <chrisl@...are.com>
>
> Andrey reports e1000e corruption, and that a patch in vmware's ESX fixed
> it.
wrong subject? the patch applies to e1000, not e1000e...
>
> 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(+)
>
> diff -puN drivers/net/e1000/e1000_hw.c~e1000e-prevent-corruption-of-eeprom-nvm drivers/net/e1000/e1000_hw.c
> --- a/drivers/net/e1000/e1000_hw.c~e1000e-prevent-corruption-of-eeprom-nvm
> +++ a/drivers/net/e1000/e1000_hw.c
> @@ -144,6 +144,8 @@ static s32 e1000_host_if_read_cookie(str
> static u8 e1000_calculate_mng_checksum(char *buffer, u32 length);
> static s32 e1000_configure_kmrn_for_10_100(struct e1000_hw *hw, u16 duplex);
> static s32 e1000_configure_kmrn_for_1000(struct e1000_hw *hw);
> +static s32 e1000_do_read_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data);
> +static s32 e1000_do_write_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data);
>
> /* IGP cable length table */
> static const
> @@ -168,6 +170,8 @@ u16 e1000_igp_2_cable_length_table[IGP02
> 83, 89, 95, 100, 105, 109, 113, 116, 119, 122, 124,
> 104, 109, 114, 118, 121, 124};
>
> +static DEFINE_SPINLOCK(e1000_eeprom_lock);
> +
> /******************************************************************************
> * Set the phy type member in the hw struct.
> *
> @@ -4904,6 +4908,15 @@ static s32 e1000_spi_eeprom_ready(struct
> *****************************************************************************/
> s32 e1000_read_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data)
> {
> + s32 ret;
> + spin_lock(&e1000_eeprom_lock);
> + ret = e1000_do_read_eeprom(hw, offset, words, data);
> + spin_unlock(&e1000_eeprom_lock);
> + return ret;
> +}
> +
> +static s32 e1000_do_read_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data)
> +{
> struct e1000_eeprom_info *eeprom = &hw->eeprom;
> u32 i = 0;
>
> @@ -5236,6 +5249,16 @@ s32 e1000_update_eeprom_checksum(struct
> *****************************************************************************/
> s32 e1000_write_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data)
> {
> + s32 ret;
> + spin_lock(&e1000_eeprom_lock);
> + ret = e1000_do_write_eeprom(hw, offset, words, data);
> + spin_unlock(&e1000_eeprom_lock);
> + return ret;
> +}
> +
> +
> +static s32 e1000_do_write_eeprom(struct e1000_hw *hw, u16 offset, u16 words, u16 *data)
> +{
> struct e1000_eeprom_info *eeprom = &hw->eeprom;
> s32 status = 0;
>
> _
> --
> 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
--
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