From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: dev@dpdk.org, nelio.laranjeiro@6wind.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix wrong exception handling
Date: Thu, 1 Jun 2017 11:24:31 +0100 [thread overview]
Message-ID: <3373c26a-702e-c11e-4239-629d4a212937@intel.com> (raw)
In-Reply-To: <20170530074823.GU1758@6wind.com>
On 5/30/2017 8:48 AM, Adrien Mazarguil wrote:
> On Mon, May 29, 2017 at 06:02:59PM -0700, Yongseok Koh wrote:
>> A sanity check is required in priv_fdir_disable(). If resizing Rx queue
>> fails, this can cause a crash by referencing a NULL pointer.
>>
>> Cc: stable@dpdk.org
>> Fixes: 76f5c99e6840 ("mlx5: support flow director")
>> Fixes: 0cdddf4d0626 ("net/mlx5: split Rx queue structure")
>>
>> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-06-01 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 1:02 Yongseok Koh
2017-05-30 7:48 ` Adrien Mazarguil
2017-06-01 10:24 ` Ferruh Yigit [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=3373c26a-702e-c11e-4239-629d4a212937@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).