From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Christoph Paasch <christoph.paasch@uclouvain.be>,
Carolyn Wyborny <carolyn.wyborny@intel.com>
Cc: Jeff Pieper <jeffrey.e.pieper@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: igb patches needed for stable
Date: Tue, 13 May 2014 09:59:49 +0200 [thread overview]
Message-ID: <20140513095949.09333569@free-electrons.com> (raw)
In-Reply-To: <20140410143603.3df4f20c@skate>
Hello,
On Thu, 10 Apr 2014 14:36:03 +0200, Thomas Petazzoni wrote:
> 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.
Any news about these patches?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-05-13 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 12:36 igb patches needed for stable Thomas Petazzoni
2014-05-13 7:59 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140513095949.09333569@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=carolyn.wyborny@intel.com \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=jeffrey.e.pieper@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox