From: Andrea Claudi <aclaudi@redhat.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
linux-netdev <netdev@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
daniel@iogearbox.net, asmadeus@codewreck.org
Subject: Re: [PATCH iproute2 v3 0/2] bpf: memory access fixes
Date: Fri, 24 Apr 2020 18:58:50 +0200 [thread overview]
Message-ID: <CAPpH65w0Lz2C+T8Zqa43OJgvM1Ky9VVsYafR9OkgFVCTnV_5dw@mail.gmail.com> (raw)
In-Reply-To: <20200423175857.20180-1-jhs@emojatatu.com>
On Thu, Apr 23, 2020 at 7:59 PM Jamal Hadi Salim <jhs@mojatatu.com> wrote:
>
> From: Jamal Hadi Salim <jhs@mojatatu.com>
>
> Changes from V2:
> 1) Dont initialize tmp on stack (Stephen)
> 2) Dont look at the return code of snprintf (Dominique)
> 3) Set errno to EINVAL instead of returning -EINVAL for consistency (Dominique)
>
> 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, 7 insertions(+), 10 deletions(-)
>
> --
> 2.20.1
>
Acked-by: Andrea Claudi <aclaudi@redhat.com>
next prev parent reply other threads:[~2020-04-24 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:58 [PATCH iproute2 v3 0/2] bpf: memory access fixes Jamal Hadi Salim
2020-04-23 17:58 ` [PATCH iproute2 v3 1/2] bpf: Fix segfault when custom pinning is used Jamal Hadi Salim
2020-04-23 17:58 ` [PATCH iproute2 v3 2/2] bpf: Fix mem leak and extraneous free() in error path Jamal Hadi Salim
2020-04-24 16:58 ` Andrea Claudi [this message]
2020-04-28 16:15 ` [PATCH iproute2 v3 0/2] bpf: memory access fixes Jamal Hadi Salim
2020-05-18 13:00 ` Jamal Hadi Salim
2020-05-23 1:33 ` Daniel Borkmann
2020-05-23 10:32 ` Jamal Hadi Salim
2020-05-25 8:53 ` Andrea Claudi
2020-05-26 12:27 ` Jamal Hadi Salim
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=CAPpH65w0Lz2C+T8Zqa43OJgvM1Ky9VVsYafR9OkgFVCTnV_5dw@mail.gmail.com \
--to=aclaudi@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.