From: Lorenz Bauer <lmb@cloudflare.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: kernel-team@cloudflare.com, Lorenz Bauer <lmb@cloudflare.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH bpf v2 0/1] bpf: fix OOB read when printing XDP link fdinfo
Date: Mon, 19 Jul 2021 09:51:33 +0100 [thread overview]
Message-ID: <20210719085134.43325-1-lmb@cloudflare.com> (raw)
See the first patch message for details. Same fix as before, except that the
macro invocation is guarded by CONFIG_NET now.
Lorenz Bauer (1):
bpf: fix OOB read when printing XDP link fdinfo
include/linux/bpf_types.h | 1 +
1 file changed, 1 insertion(+)
--
2.30.2
next reply other threads:[~2021-07-19 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 8:51 Lorenz Bauer [this message]
2021-07-19 8:51 ` [PATCH bpf v2 1/1] bpf: fix OOB read when printing XDP link fdinfo Lorenz Bauer
2021-07-19 23:11 ` John Fastabend
2021-07-19 22:31 ` [PATCH bpf v2 0/1] " Andrii Nakryiko
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=20210719085134.43325-1-lmb@cloudflare.com \
--to=lmb@cloudflare.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@cloudflare.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).