Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: 'Matt Porter' <mporter@konsulko.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v5 1/4] igb: add support of RX network flow classification
Date: Wed, 6 Jul 2016 08:29:11 -0400	[thread overview]
Message-ID: <20160706122911.GA21676@beef> (raw)
In-Reply-To: <CY1PR04MB22667E5A6AF951CC05BF9DB7EC3A0@CY1PR04MB2266.namprd04.prod.outlook.com>

On Wed, Jul 06, 2016 at 08:28:46AM +0000, Gangfeng Huang wrote:
> Hi matt,
> 
> I have add your fix to the v6 patches and resubmit them, please help to test it.

Ok, thanks. I'll retest with v6 and reply back to that thread. I hope
you are feeling better.

-Matt

> -----Original Message-----
> From: 'Matt Porter' [mailto:mporter at konsulko.com] 
> Sent: 2016?7?1? 4:11
> To: Brown, Aaron F <aaron.f.brown@intel.com>
> Cc: Gangfeng Huang <gangfeng.huang@ni.com>; 'intel-wired-lan at lists.osuosl.org' <intel-wired-lan@lists.osuosl.org>; Ruhao Gao <ruhao.gao@ni.com>
> Subject: Re: [Intel-wired-lan] [PATCH net-next v5 1/4] igb: add support of RX network flow classification
> 
> On Thu, Jun 30, 2016 at 07:51:01PM +0000, Brown, Aaron F wrote:
> > 
> > 
> > > -----Original Message-----
> > > From: 'Matt Porter' [mailto:mporter at konsulko.com]
> > > Sent: Thursday, June 30, 2016 9:16 AM
> > > To: Brown, Aaron F <aaron.f.brown@intel.com>
> > > Cc: 'Gangfeng' <gangfeng.huang@ni.com>; 'intel-wired-lan at lists.osuosl.org'
> > > <intel-wired-lan@lists.osuosl.org>; 'Ruhao Gao' <ruhao.gao@ni.com>
> > > Subject: Re: [Intel-wired-lan] [PATCH net-next v5 1/4] igb: add 
> > > support of RX network flow classification
> > >
> > <snip>
> > > 
> > > Ok, the full oops output made me notice the problem. Can you try the 
> > > following untested fix on your failing system? It'll apply against 
> > > patch 1/4 and is build tested against the next-queue dev-queue branch.
> > > 
> > > -Matt
> > > 
> > > From 8773d0f09741d7a318cdd96cf5aad2ddb79096e7 Mon Sep 17 00:00:00
> > > 2001
> > > From: Matt Porter <mporter@konsulko.com>
> > > Date: Thu, 30 Jun 2016 11:47:50 -0400
> > > Subject: [PATCH] igb: Fix missing lock init in rx network flow 
> > > classification  support
> > > 
> > > "[net-next,v5,1/4] igb: add support of RX network flow classification"
> > > adds a new nfc_lock to each adapter to protect the rx filter hash list.
> > > This lock is not initialized before use which results in 
> > > intermittent oopses. Initialize this lock during probe to fix the issue.
> > > 
> > > Signed-off-by: Matt Porter <mporter@konsulko.com>
> > > ---
> > >  drivers/net/ethernet/intel/igb/igb_main.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
> > > b/drivers/net/ethernet/intel/igb/igb_main.c
> > > index c04b1c2..e5a4949 100644
> > > --- a/drivers/net/ethernet/intel/igb/igb_main.c
> > > +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> > > @@ -3075,6 +3075,7 @@ static int igb_sw_init(struct igb_adapter *adapter)
> > >  				  VLAN_HLEN;
> > >  	adapter->min_frame_size = ETH_ZLEN + ETH_FCS_LEN;
> > > 
> > > +	spin_lock_init(&adapter->nfc_lock);
> > >  	spin_lock_init(&adapter->stats64_lock);
> > >  #ifdef CONFIG_PCI_IOV
> > >  	switch (hw->mac.type) {
> > > --
> > > 2.7.0
> > 
> > Bingo!  That resolved it.  I can now load and bind (with ifconfig) on all the systems that were previously giving me the splat without seeing anything out of the ordinary.
> 
> Excellent! Thanks for doing the grunt testing work on it. ;) Looks like this was the only remaining issue from the v5 submission.
> 
> Gangfeng: can you fold this fix into a v6 submission? If this isn't something you are still working on then let me know and I can resubmit.
> 
> Regards,
> Matt
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at lists.osuosl.org
> http://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2016-07-06 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  9:27 [Intel-wired-lan] [PATCH net-next v5 0/4] igb: enable RX network flow classification Gangfeng
2016-05-09  9:27 ` [Intel-wired-lan] [PATCH net-next v5 1/4] igb: add support of " Gangfeng
2016-05-16 22:09   ` Brown, Aaron F
2016-05-17  1:45     ` Brown, Aaron F
2016-06-29 19:12     ` Matt Porter
2016-06-29 20:06       ` Brown, Aaron F
2016-06-30  1:20         ` Brown, Aaron F
2016-06-30 15:28           ` 'Matt Porter'
2016-06-30 16:16           ` 'Matt Porter'
2016-06-30 19:51             ` Brown, Aaron F
2016-06-30 20:10               ` 'Matt Porter'
2016-07-04  3:12                 ` Gangfeng Huang
2016-07-06  8:28                 ` Gangfeng Huang
2016-07-06 12:29                   ` 'Matt Porter' [this message]
2016-05-09  9:27 ` [Intel-wired-lan] [PATCH net-next v5 2/4] igb: support RX flow classification by ethertype Gangfeng
2016-05-09  9:27 ` [Intel-wired-lan] [PATCH net-next v5 3/4] igb: support RX flow classification by VLAN priority Gangfeng
2016-05-09  9:27 ` [Intel-wired-lan] [PATCH net-next v5 4/4] igb: fix error code in igb_add_ethtool_nfc_entry() Gangfeng
2016-05-16 22:21 ` [Intel-wired-lan] [PATCH net-next v5 0/4] igb: enable RX network flow classification Jeff Kirsher

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=20160706122911.GA21676@beef \
    --to=mporter@konsulko.com \
    --cc=intel-wired-lan@osuosl.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