From: Daniel Borkmann <daniel@iogearbox.net>
To: Ciara Loftus <ciara.loftus@intel.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
magnus.karlsson@intel.com, bjorn@kernel.org,
andrii.nakryiko@gmail.com, alexei.starovoitov@gmail.com
Subject: Re: [PATCH bpf] libbpf: fix potential NULL pointer dereference
Date: Thu, 8 Apr 2021 23:38:41 +0200 [thread overview]
Message-ID: <8d129061-ec08-06b6-95a2-0eeefc5ed981@iogearbox.net> (raw)
In-Reply-To: <20210408052009.7844-1-ciara.loftus@intel.com>
On 4/8/21 7:20 AM, Ciara Loftus wrote:
> Wait until after the UMEM is checked for null to dereference it.
>
> Fixes: 43f1bc1efff1 ("libbpf: Restore umem state after socket create failure")
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Applied, thanks!
prev parent reply other threads:[~2021-04-08 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 5:20 [PATCH bpf] libbpf: fix potential NULL pointer dereference Ciara Loftus
2021-04-08 21:38 ` Daniel Borkmann [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=8d129061-ec08-06b6-95a2-0eeefc5ed981@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ciara.loftus@intel.com \
--cc=magnus.karlsson@intel.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).