From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Blunck <jblunck@infradead.org>, Alan Dewar <adewar@brocade.com>
Cc: dev@dpdk.org, "Dumitrescu,
Cristian" <cristian.dumitrescu@intel.com>,
"h.mikita89@gmail.com" <h.mikita89@gmail.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] sched: fix segmentation fault when freeing port
Date: Thu, 09 Feb 2017 18:48:16 +0100 [thread overview]
Message-ID: <16895121.pfXIAiMIQd@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D8912652748706@IRSMSX108.ger.corp.intel.com>
> > Prevent a segmentation fault in rte_sched_port_free by only accessing
> > the port structure after the NULL pointer check has been made.
> >
> > Fixes: 7b3c4f35 ("sched: fix releasing enqueued packets")
> >
> > Signed-off-by: Alan Dewar <adewar@brocade.com>
> > Signed-off-by: Jan Blunck <jblunck@infradead.org>
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: stable@dpdk.org
Applied, thanks
prev parent reply other threads:[~2017-02-09 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:32 Jan Blunck
2017-02-06 18:42 ` Dumitrescu, Cristian
2017-02-09 17:48 ` Thomas Monjalon [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=16895121.pfXIAiMIQd@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=adewar@brocade.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=h.mikita89@gmail.com \
--cc=jblunck@infradead.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).