From: Thomas Monjalon <thomas@monjalon.net>
To: Remy Horton <remy.horton@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] lib/bitratestats: add NULL sanity checks
Date: Thu, 26 Jul 2018 20:07:03 +0200 [thread overview]
Message-ID: <4850918.9fX15AOWJ3@xps> (raw)
In-Reply-To: <2d0db3f0-3eeb-99bd-33bb-731965d2228f@intel.com>
20/07/2018 17:31, Ferruh Yigit:
> On 7/12/2018 11:49 AM, Remy Horton wrote:
> > If rte_stats_bitrate_reg() or rte_stats_bitrate_calc() are
> > passed NULL as the parameter for the stats structure, the
> > result is a crash. Fixed by adding a sanity check that makes
> > sure the passed-in pointer is not NULL.
> >
> > Fixes: 2ad7ba9a6567 ("bitrate: add bitrate statistics library")
> >
> > Signed-off-by: Remy Horton <remy.horton@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-07-26 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 13:21 [dpdk-dev] [PATCH v1] lib/bitratestats: add NULL sanity check Remy Horton
2018-07-12 10:49 ` [dpdk-dev] [PATCH v2] lib/bitratestats: add NULL sanity checks Remy Horton
2018-07-20 15:31 ` Ferruh Yigit
2018-07-26 18:07 ` 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=4850918.9fX15AOWJ3@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=remy.horton@intel.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).