BPF List
 help / color / mirror / Atom feed
From: Leon Hwang <leon.hwang@linux.dev>
To: bot+bpf-ci@kernel.org, bpf@vger.kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, ihor.solodrai@linux.dev, hawk@kernel.org,
	john.fastabend@gmail.com, sdf@fomichev.me, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	shuah@kernel.org, kuniyu@google.com, liuhangbin@gmail.com,
	mkarsten@uwaterloo.ca, masashi.honma@gmail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, martin.lau@kernel.org,
	mason@kernel.org
Subject: Re: [PATCH bpf-next 6/6] selftests/bpf: Add tests to verify link_create logs
Date: Mon, 19 Oct 2026 00:33:43 +0800	[thread overview]
Message-ID: <b97fa998-b77d-4600-8453-9bb16200409e@linux.dev> (raw)
In-Reply-To: <343fe8b9f06af37dde193869b694dbf908b0a0f6592a1e4cc5f5a0ac295b1b88@mail.kernel.org>

On 2026/10/17 23:02, bot+bpf-ci@kernel.org wrote:
>> selftests/bpf: Add tests to verify link_create logs
> 
> TL;DR: Nits only, in the new link_create log selftests in xdp_link.c: the four
> subtests repeat the same setup and assertions and could share a helper, and
> one has a redundant true_size = 0.
> 
>> diff --git a/tools/testing/selftests/bpf/prog_tests/xdp_link.c b/tools/testing/selftests/bpf/prog_tests/xdp_link.c
>> --- a/tools/testing/selftests/bpf/prog_tests/xdp_link.c
>> +++ b/tools/testing/selftests/bpf/prog_tests/xdp_link.c
> 
> [ ... ]
> 
>> @@ -150,3 +150,135 @@ void serial_test_xdp_link(void)
>>  	test_xdp_link__destroy(skel1);
>>  	test_xdp_link__destroy(skel2);
>>  }
>> +
>> +static void test_link_create_invalid_prog_fd(void)
>> +{
>> +	const char *msg = "Invalid prog_fd.\n";
>> +	char log_buf[128] = {};
>> +	int fd;
>> +	LIBBPF_OPTS(bpf_log_opts, log_opts,
>> +		    .buf = log_buf,
>> +		    .size = sizeof(log_buf),
>> +		    .level = 1,
>> +	);
>> +
>> +	fd = bpf_link_create_log(-1, IFINDEX_LO, BPF_XDP, NULL, &log_opts);
>> +	if (!ASSERT_LT(fd, 0, "bpf_link_create_log")) {
>> +		close(fd);
>> +		return;
>> +	}
>> +
>> +	ASSERT_EQ(fd, -EBADF, "fd");
>> +	ASSERT_STREQ(log_buf, msg, "log_buf");
>> +	ASSERT_EQ(log_opts.true_size, strlen(msg) + 1, "log_size");
>> +}
> 
> This isn't a bug, but the four new test_link_create_*() functions repeat the
> same log_buf and LIBBPF_OPTS(bpf_log_opts, ...) setup, and the same trailing
> ASSERT_EQ(fd, ...) / ASSERT_STREQ(log_buf, msg) /
> ASSERT_EQ(log_opts.true_size, strlen(msg) + 1) sequence.  They differ only in
> prog fd, target, attach type, expected errno and message.

Will factor out helpers to simplify the tests code.

> 
> This looks close to test_map_create() in map_init.c.  Could the four
> link_create log tests share a small helper that takes the prog fd, target,
> attach type, opts, expected errno and message?
> 
>> +
>> +static void test_link_create_invalid_attach_type(void)
>> +{
>> +	const char *msg = "Invalid attach_type.\n";
>> +	struct test_xdp_link *skel;
>> +	char log_buf[128] = {};
>> +	int fd;
>> +	LIBBPF_OPTS(bpf_log_opts, log_opts,
>> +		    .buf = log_buf,
>> +		    .size = sizeof(log_buf),
>> +		    .level = 1,
>> +	);
>> +
>> +	skel = test_xdp_link__open_and_load();
>> +	if (!ASSERT_OK_PTR(skel, "test_xdp_link__open_and_load"))
>> +		return;
>> +
>> +	log_opts.true_size = 0;
> 
> This isn't a bug, but is the log_opts.true_size = 0; line needed here?
> LIBBPF_OPTS() already zero-initializes log_opts, true_size is only written by
> libbpf after the syscall, and the other three tests omit this line.

Good catch.

This line is unnecessary. Will drop it in the next revision.

Thanks,
Leon


      reply	other threads:[~2026-10-18 16:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 14:26 [PATCH bpf-next 0/6] bpf: Add syscall common attrs support for xdp link_create Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 1/6] bpf: Add syscall common attrs support for link_create Leon Hwang
2026-10-17 14:39   ` sashiko-bot
2026-10-18 16:28     ` Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 2/6] bpf: Add syscall common attrs support for xdp link_create Leon Hwang
2026-10-17 14:48   ` sashiko-bot
2026-10-18 16:32     ` Leon Hwang
2026-10-17 15:03   ` bot+bpf-ci
2026-10-18 16:30     ` Leon Hwang
2026-10-18  3:28   ` kernel test robot
2026-10-18 16:29     ` Leon Hwang
2026-10-18  3:46   ` kernel test robot
2026-10-18 16:29     ` Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 3/6] bpf: Retire tracepoint bpf_xdp_link_attach_failed Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 4/6] libbpf: Factor out __bpf_sys_fd helper Leon Hwang
2026-10-17 14:53   ` bot+bpf-ci
2026-10-18 16:32     ` Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 5/6] libbpf: Add bpf_link_create_log API Leon Hwang
2026-10-17 14:43   ` sashiko-bot
2026-10-18 16:33     ` Leon Hwang
2026-10-17 15:03   ` bot+bpf-ci
2026-10-18 16:33     ` Leon Hwang
2026-10-17 14:26 ` [PATCH bpf-next 6/6] selftests/bpf: Add tests to verify link_create logs Leon Hwang
2026-10-17 15:02   ` bot+bpf-ci
2026-10-18 16:33     ` Leon Hwang [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=b97fa998-b77d-4600-8453-9bb16200409e@linux.dev \
    --to=leon.hwang@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=emil@etsalapatis.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=masashi.honma@gmail.com \
    --cc=mason@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=memxor@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=mkarsten@uwaterloo.ca \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox