| 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: <20100418.220931.39174434.davem@davemloft.net> Date: Sun, 18 Apr 2010 22:09:31 -0700 (PDT) From: David Miller <davem@...emloft.net> To: jeffrey.t.kirsher@...el.com Cc: netdev@...r.kernel.org, gospo@...hat.com, nicholasx.d.nunley@...el.com, john.ronciak@...el.com Subject: Re: [net-2.6 PATCH] ixgbe: add IntMode module parameter From: Jeff Kirsher <jeffrey.t.kirsher@...el.com> Date: Sun, 18 Apr 2010 22:03:59 -0700 > This patch adds the IntMode module parameter to ixgbe to allow > user selection of interrupt mode (MSI-X, MSI, legacy) on driver > load. To work around the errata described above, ixgbe needs to > be able to disable MSI-X for affected configurations. This is not how we handle situations like this. Here is one acceptable way to handle this: Turn MSI/MSI-X off for every system that uses this PCI-E complex chipset. Add a whitelist that allows enabling. Here is another: Turn MSI/MSI-X on by default and have blacklists. Anything that requires unusual user interactions, such as specifying special module parameters, for correct operations is absolutely unacceptable. I don't want to hear how difficult it is to determine whether a system will hit this bug or not. If it's hard, just turn MSI off unconditionally with this chipset until you can detect things properly. -- 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