From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Kohei Enju <enjuk@amazon.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
kohei.enju@gmail.com, Kohei Enju <enjuk@amazon.com>
Subject: Re: [PATCH bpf-next v2 2/2] selftests/bpf: add tests for attaching invalid fd
Date: Mon, 08 Dec 2025 15:20:44 +0100 [thread overview]
Message-ID: <87ldjd6on7.fsf@toke.dk> (raw)
In-Reply-To: <20251208131449.73036-3-enjuk@amazon.com>
Kohei Enju <enjuk@amazon.com> writes:
> Add test cases for situations where adding the following types of file
> descriptors to a cpumap entry should fail:
> - Non-BPF file descriptor (expect -EINVAL)
> - Nonexistent file descriptor (expect -EBADF)
>
> Also tighten the assertion for the expected error when adding a
> non-BPF_XDP_CPUMAP program to a cpumap entry.
>
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat.com>
next prev parent reply other threads:[~2025-12-08 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 13:14 [PATCH bpf-next v2 0/2] bpf: cpumap: improve error propagation in cpu_map_update_elem() Kohei Enju
2025-12-08 13:14 ` [PATCH bpf-next v2 1/2] bpf: cpumap: propagate underlying error " Kohei Enju
2025-12-08 14:19 ` Toke Høiland-Jørgensen
2025-12-08 13:14 ` [PATCH bpf-next v2 2/2] selftests/bpf: add tests for attaching invalid fd Kohei Enju
2025-12-08 14:20 ` Toke Høiland-Jørgensen [this message]
2025-12-10 8:00 ` [PATCH bpf-next v2 0/2] bpf: cpumap: improve error propagation in cpu_map_update_elem() patchwork-bot+netdevbpf
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=87ldjd6on7.fsf@toke.dk \
--to=toke@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=enjuk@amazon.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kohei.enju@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.