| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <21d7e9970809240216m4a93a339sb51a5928fcb5f6fb@mail.gmail.com> Date: Wed, 24 Sep 2008 19:16:24 +1000 From: "Dave Airlie" <airlied@...il.com> To: "David Miller" <davem@...emloft.net> Cc: jkosina@...e.cz, jeffrey.t.kirsher@...el.com, david.vrabel@....com, rjw@...k.pl, linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org, chrisl@...are.com Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM On Wed, Sep 24, 2008 at 7:01 PM, David Miller <davem@...emloft.net> wrote: > From: "Dave Airlie" <airlied@...il.com> > Date: Wed, 24 Sep 2008 18:59:34 +1000 > >> On Wed, Sep 24, 2008 at 5:36 PM, David Miller <davem@...emloft.net> wrote: >> The driver seems quite happy to access the NVRAM, I think Thomas has >> some backtraces that show >> it clearly doing silly reentrant things... > > I don't dispute that the locking is dodgy and likely needs to be fixed > like e1000. > > I'm asking what userland tool or kernel event is triggering the nvram > access. > > It shouldn't even touch the thing after probing and initializing > the card. Hopefully tglx can supply some traces, I think getting an interrupt during device startup can possibly access the nvram http://www.tglx.de/~tglx/wtf2.txt seems to suggest bad things could happen. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists