[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080903.012432.75866225.davem@davemloft.net>
Date: Wed, 03 Sep 2008 01:24:32 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: zach@...are.com
Cc: jesse.brandeburg@...el.com, chrisl@...are.com,
akpm@...ux-foundation.org, arvidjaar@...l.ru,
bruce.w.allan@...el.com, jeff@...zik.org,
jeffrey.t.kirsher@...el.com, john.ronciak@...el.com,
peter.p.waskiewicz.jr@...el.com, pratap@...are.com,
netdev@...r.kernel.org, mm-commits@...r.kernel.org
Subject: Re: + e1000e-prevent-corruption-of-eeprom-nvm.patch added to
-mmtree
From: Zachary Amsden <zach@...are.com>
Date: Wed, 03 Sep 2008 01:17:25 -0700
> Thus, the obvious answer to me is ... LOCK AROUND EEPROM READS AND
> WRITES now and figure out if there are deeper issues due to network
> layer and E1000 complexities later, but ELIMINATE THE CATASTROPHIC
> FAILURES ASAP.
I totally agree with Zach here.
The fact that we are still masterbating about this bug and a fix
isn't in the tree is absolutely rediculious.
--
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