From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com, aclaudi@redhat.com,
daniel@iogearbox.net, asmadeus@codewreck.org,
Jamal Hadi Salim <hadi@mojatatu.com>
Subject: Re: [PATCH iproute2 v2 0/2] bpf: memory access fixes
Date: Wed, 29 Apr 2020 22:40:30 -0700 [thread overview]
Message-ID: <20200429224030.736d655a@hermes.lan> (raw)
In-Reply-To: <20200422102808.9197-1-jhs@emojatatu.com>
On Wed, 22 Apr 2020 06:28:06 -0400
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> From: Jamal Hadi Salim <hadi@mojatatu.com>
>
> Changes from V1:
> 1) use snprintf instead of sprintf and fix corresponding error message.
> Caught-by: Dominique Martinet <asmadeus@codewreck.org>
> 2) Fix memory leak and extraneous free() in error path
>
> Jamal Hadi Salim (2):
> bpf: Fix segfault when custom pinning is used
> bpf: Fix mem leak and extraneous free() in error path
>
> lib/bpf.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
Would be good to see a v3 and ideally ACK's from of the
other BPF developers such as Daniel Borkmann
or Jakub Kiciniski
prev parent reply other threads:[~2020-04-30 5:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 10:28 [PATCH iproute2 v2 0/2] bpf: memory access fixes Jamal Hadi Salim
2020-04-22 10:28 ` [PATCH iproute2 v2 1/2] bpf: Fix segfault when custom pinning is used Jamal Hadi Salim
2020-04-22 12:24 ` Andrea Claudi
2020-04-22 14:43 ` Dominique Martinet
2020-04-22 17:07 ` Jamal Hadi Salim
2020-04-22 16:35 ` Stephen Hemminger
2020-04-22 17:19 ` Jamal Hadi Salim
2020-04-23 6:30 ` Dominique Martinet
2020-04-23 17:46 ` Jamal Hadi Salim
2020-04-22 10:28 ` [PATCH iproute2 v2 2/2] bpf: Fix mem leak and extraneous free() in error path Jamal Hadi Salim
2020-04-22 14:44 ` Dominique Martinet
2020-04-30 5:40 ` Stephen Hemminger [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=20200429224030.736d655a@hermes.lan \
--to=stephen@networkplumber.org \
--cc=aclaudi@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=hadi@mojatatu.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.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).