From: David Marchand <david.marchand@redhat.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: wangyunjian <wangyunjian@huawei.com>, dev <dev@dpdk.org>,
"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
dpdk stable <stable@dpdk.org>, xudingke <xudingke@huawei.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2 0/3] kvargs fixes
Date: Fri, 27 Mar 2020 18:12:32 +0100 [thread overview]
Message-ID: <CAJFAV8zgo5h4RK89gN8BNiHN=d-o6VnYJQEprW=k6dCpbappLw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x9ig0Bv0NVVkaEPU_mEZK-Wy92f2arEZcXWrnag0VHcw@mail.gmail.com>
On Fri, Mar 27, 2020 at 4:16 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Fri, Mar 27, 2020 at 9:10 AM Olivier Matz <olivier.matz@6wind.com> wrote:
> >
> > This patchset fixes a buffer overflow in kvargs when parsing an invalid
> > string, and fixes the kvargs unit tests.
> >
> > Olivier Matz (2):
> > tests/kvargs: fix to consider empty elements as valid
> > tests/kvargs: fix check of invalid cases
> >
> > Yunjian Wang (1):
> > kvargs: fix a heap buffer overflow when parsing list
>
> For the series,
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-03-27 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 4:38 [dpdk-dev] [PATCH] kvargs: fix a heap-buffer-overflow when detect list wangyunjian
2020-03-25 16:31 ` Olivier Matz
2020-03-26 10:01 ` [dpdk-dev] 答复: " wangyunjian
2020-03-27 8:09 ` [dpdk-dev] [PATCH v2 0/3] kvargs fixes Olivier Matz
2020-03-27 8:09 ` [dpdk-dev] [PATCH v2 1/3] tests/kvargs: fix to consider empty elements as valid Olivier Matz
2020-03-27 8:09 ` [dpdk-dev] [PATCH v2 2/3] tests/kvargs: fix check of invalid cases Olivier Matz
2020-03-27 8:09 ` [dpdk-dev] [PATCH v2 3/3] kvargs: fix a heap buffer overflow when parsing list Olivier Matz
2020-03-27 15:16 ` [dpdk-dev] [dpdk-stable] [PATCH v2 0/3] kvargs fixes David Marchand
2020-03-27 17:12 ` David Marchand [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='CAJFAV8zgo5h4RK89gN8BNiHN=d-o6VnYJQEprW=k6dCpbappLw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--cc=xudingke@huawei.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).