DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Rich Lane <rich.lane@bigswitch.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Helin" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix null pointer dereferences when using VMDQ+RSS
Date: Fri, 23 Sep 2016 11:56:20 +0100	[thread overview]
Message-ID: <20160923105620.GA58488@bricha3-MOBL3> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F80E2714C3@SHSMSX103.ccr.corp.intel.com>

On Thu, Sep 22, 2016 at 08:20:25AM +0000, Wu, Jingjing wrote:
> 
> 
> > -----Original Message-----
> > From: Yigit, Ferruh
> > Sent: Wednesday, September 14, 2016 10:00 PM
> > To: Rich Lane; dev@dpdk.org
> > Cc: Zhang, Helin; Wu, Jingjing
> > Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix null pointer dereferences
> > when using VMDQ+RSS
> > 
> > On 8/2/2016 8:34 PM, Rich Lane wrote:
> > > When using VMDQ+RSS, the queue ids used by the application are not
> > > contiguous (see i40e_pf_config_rss). Most of the driver already
> > > handled this, but there were a few cases where it assumed all
> > > configured queues had been setup.
> > >
> > > Fixes: 4861cde46116 ("i40e: new poll mode driver")
> > > Fixes: 6b4537128394 ("i40e: free queue memory when closing")
> > > Fixes: 8e109464c022 ("i40e: allow vector Rx and Tx usage")
> > >
> > > Signed-off-by: Rich Lane <rich.lane@bigswitch.com>
> 
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> 
>
Applied to dpdk-next-net/rel_16_11

/Bruce

      reply	other threads:[~2016-09-23 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 19:34 Rich Lane
2016-09-14 14:00 ` Ferruh Yigit
2016-09-22  8:20   ` Wu, Jingjing
2016-09-23 10:56     ` Bruce Richardson [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=20160923105620.GA58488@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=rich.lane@bigswitch.com \
    /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;
as well as URLs for NNTP newsgroup(s).