netdev - igb patches needed for stable

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-next>] [day] [month] [year] [list]

Message-ID: <20140410143603.3df4f20c@skate>
Date:	Thu, 10 Apr 2014 14:36:03 +0200
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	Christoph Paasch <christoph.paasch@...ouvain.be>,
	Carolyn Wyborny <carolyn.wyborny@...el.com>,
	Jeff Pieper <jeffrey.e.pieper@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc:	netdev@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: igb patches needed for stable

Hello,

I just wanted to let you know that the following two patches:

  cb06d102327eadcd1bdc480bfd9f8876251d1007 igb: Fix Null-pointer dereference in igb_reset_q_vector
  b709323d2477614823a38c2f2a9a206e087e28fc igb: Unset IGB_FLAG_HAS_MSIX-flag when falling back to msi-only

should probably be backported to stable 3.14 versions. The above
patches are part of Linus tree, but merged after v3.14 has been
released. However, they fix a regression introduced by cd14ef54d25b
(igb: Change to use statically allocated array for MSIx entries), which
is part of v3.14.

And I'm actually experiencing a crash igb_reset_q_vector() on a system
which has MSI support, but not MSI-X support, and basically the code
path of the driver which fallbacks from MSI-X to MSI is the one
crashing. With both of these patches applied on top of 3.14, my igb NIC
works fine.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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