From: Stanislav Fomichev <sdf@google.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org
Subject: [PATCH bpf-next 0/2] bpf: fix couple of netdevsim issues
Date: Mon, 13 Nov 2023 20:54:51 -0800 [thread overview]
Message-ID: <20231114045453.1816995-1-sdf@google.com> (raw)
The first one is found by the syzkaller and needs to make a proper
distinction between offloaded and dev-bound cases.
The second one restores behavior where the offloaded/dev-bound programs
with a dead netdev were not correctly skipped during BPF_PROG_GET_NEXT_ID.
Stanislav Fomichev (2):
netdevsim: don't accept device bound programs
bpf: bring back removal of dev-bound id from idr
drivers/net/netdevsim/bpf.c | 4 ++--
include/linux/bpf.h | 2 ++
kernel/bpf/offload.c | 3 +++
kernel/bpf/syscall.c | 15 +++++++++++----
4 files changed, 18 insertions(+), 6 deletions(-)
--
2.42.0.869.gea05f2083d-goog
next reply other threads:[~2023-11-14 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 4:54 Stanislav Fomichev [this message]
2023-11-14 4:54 ` [PATCH bpf-next 1/2] netdevsim: don't accept device bound programs Stanislav Fomichev
2023-11-20 21:38 ` Stanislav Fomichev
2023-11-20 21:58 ` Jakub Kicinski
2023-11-14 4:54 ` [PATCH bpf-next 2/2] bpf: bring back removal of dev-bound id from idr Stanislav Fomichev
2023-11-20 21:39 ` Stanislav Fomichev
2023-11-21 21:03 ` Martin KaFai Lau
2023-11-22 15:07 ` Daniel Borkmann
2023-11-22 18:05 ` Stanislav Fomichev
2023-11-22 18:40 ` Martin KaFai Lau
2023-11-22 22:41 ` Stanislav Fomichev
2023-11-22 22:54 ` Daniel Borkmann
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=20231114045453.1816995-1-sdf@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=yhs@fb.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 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.