linux-kernel - Re: NVIDIA Ethernet & invalid MAC

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4714E1C7.1090502@garzik.org>
Date:	Tue, 16 Oct 2007 12:07:35 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chris Snook <csnook@...hat.com>
CC:	Konstantin Kalin <konstantin.kalin@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: NVIDIA Ethernet & invalid MAC

Chris Snook wrote:
> Konstantin Kalin wrote:
>> P.S. It's simple to add DEV_HAS_CORRECT_MACADDR to pci_device_tlb for 
>> these types of Ethernet. But I think it's not right decision because 
>> it would break older revisions of these models.
> 
> Any reason you can't distinguish based on PCI ID?

That's presumably what he means, when he references the PCI device ID table.

But to establish that on a per-ID basis, we have to get some idea of the 
sample set.  You cannot just make the decision based on PCI ID alone, 
because that PCI ID can (and does) apply to multiple BIOS vendors.

	Jeff



-
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/