mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bot+bpf-ci@kernel.org
To: bastien.curutchet@bootlin.com,bjorn@kernel.org,magnus.karlsson@intel.com,maciej.fijalkowski@intel.com,jonathan.lemon@gmail.com,ast@kernel.org,daniel@iogearbox.net,andrii@kernel.org,martin.lau@linux.dev,eddyz87@gmail.com,song@kernel.org,yonghong.song@linux.dev,john.fastabend@gmail.com,kpsingh@kernel.org,sdf@fomichev.me,haoluo@google.com,jolsa@kernel.org,mykolal@fb.com,shuah@kernel.org,davem@davemloft.net,kuba@kernel.org,hawk@kernel.org
Cc: thomas.petazzoni@bootlin.com,alexis.lothore@bootlin.com,netdev@vger.kernel.org,bpf@vger.kernel.org,linux-kselftest@vger.kernel.org,linux-kernel@vger.kernel.org,bastien.curutchet@bootlin.com,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,clm@meta.com,ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v6 11/15] selftests/bpf: test_xsk: Don't exit immediately when workers fail
Date: Wed, 29 Oct 2025 14:25:54 +0000 (UTC)	[thread overview]
Message-ID: <5c1c4101d42cc486366273556492d9be559f521d16629bbcd6b3adc6a4b746f0@mail.kernel.org> (raw)
In-Reply-To: <20251029-xsk-v6-11-5a63a64dff98@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 4167 bytes --]


```
commit f89231e503dc0b97c81f4bb32d28532fb3471acd
Author: Bastien Curutchet (eBPF Foundation) <bastien.curutchet@bootlin.com>

selftests/bpf: test_xsk: Don't exit immediately when workers fail

This commit converts the test program from using exit_with_error()
(which immediately terminates) to proper error propagation through
return values. This allows the test suite to continue running after
failures.

> diff --git a/tools/testing/selftests/bpf/test_xsk.c b/tools/testing/selftests/bpf/test_xsk.c
> index 2c955e109..2c392d5b9 100644
> --- a/tools/testing/selftests/bpf/test_xsk.c
> +++ b/tools/testing/selftests/bpf/test_xsk.c

[ ... ]

> @@ -759,7 +761,7 @@ static bool is_metadata_correct(struct pkt *pkt, void *buffer, u64 addr)
>  	return true;
>  }
>
> -static bool is_adjust_tail_supported(struct xsk_xdp_progs *skel_rx)
> +static int is_adjust_tail_supported(struct xsk_xdp_progs *skel_rx, bool *supported)
>  {
>  	struct bpf_map *data_map;
>  	int adjust_value = 0;
> @@ -769,19 +771,21 @@ static bool is_adjust_tail_supported(struct xsk_xdp_progs *skel_rx)
>  	data_map = bpf_object__find_map_by_name(skel_rx->obj, "xsk_xdp_.bss");
>  	if (!data_map || !bpf_map__is_internal(data_map)) {
>  		ksft_print_msg("Error: could not find bss section of XDP program\n");
> -		exit_with_error(errno);
> +		return -EINVAL;
>  	}
>
>  	ret = bpf_map_lookup_elem(bpf_map__fd(data_map), &key, &adjust_value);
>  	if (ret) {
>  		ksft_print_msg("Error: bpf_map_lookup_elem failed with error %d\n", ret);
> -		exit_with_error(errno);
> +		return ret;
>  	}
>
>  	/* Set the 'adjust_value' variable to -EOPNOTSUPP in the XDP program if the adjust_tail
>  	 * helper is not supported. Skip the adjust_tail test case in this scenario.
>  	 */
> -	return adjust_value != -EOPNOTSUPP;
> +	*supported = adjust_value != -EOPNOTSUPP;
> +
> +	return 0;
>  }

[ ... ]

> @@ -1584,29 +1614,41 @@ void *worker_testapp_validate_rx(void *arg)
>  	int err;
>
>  	if (test->current_step == 1) {
> -		thread_common_ops(test, ifobject);
> +		err = thread_common_ops(test, ifobject);
>  	} else {
>  		xsk_clear_xskmap(ifobject->xskmap);
>  		err = xsk_update_xskmap(ifobject->xskmap, ifobject->xsk->xsk, 0);
> -		if (err) {
> +		if (err)
>  			ksft_print_msg("Error: Failed to update xskmap, error %s\n",
>  				       strerror(-err));
> -			exit_with_error(-err);
> -		}
>  	}
>
>  	pthread_barrier_wait(&barr);
>
> +	/* We leave only now in case of error to avoid getting stuck in the barrier */
> +	if (err) {
> +		test->fail = true;
> +		pthread_exit(NULL);
> +	}
> +
>  	err = receive_pkts(test);
>
>  	if (!err && ifobject->validation_func)
>  		err = ifobject->validation_func(ifobject);
>
>  	if (err) {
> -		if (test->adjust_tail && !is_adjust_tail_supported(ifobject->xdp_progs))
> -			test->adjust_tail_support = false;
> -		else
> +		if (!test->adjust_tail) {
>  			test->fail = true;
> +		} else {
> +			bool supported;
> +
> +			if (is_adjust_tail_supported(ifobject->xdp_progs, &supported))
> +				test->fail = true;
> +			if (!supported)
> +				test->adjust_tail_support = false;
> +			else
> +				test->fail = true;
> +		}
>  	}

Can the 'supported' variable be read uninitialized here? When
is_adjust_tail_supported() returns an error (non-zero), it doesn't
write to the *supported output parameter. The function returns early
from either the data_map check or bpf_map_lookup_elem() failure without
setting *supported. Then the code unconditionally checks "if (!supported)"
which would read uninitialized stack memory.

The control flow is:
  is_adjust_tail_supported() returns error
  -> test->fail = true is set
  -> execution continues to "if (!supported)"
  -> reads uninitialized 'supported' variable

Should this be structured with an else clause to only check 'supported'
when is_adjust_tail_supported() returns success?


```

---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

In-Reply-To-Subject: `selftests/bpf: test_xsk: Don't exit immediately when workers fail`
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/18910697393

  reply	other threads:[~2025-10-29 14:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 13:52 [PATCH bpf-next v6 00/15] selftests/bpf: Integrate test_xsk.c to test_progs framework Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 01/15] selftests/bpf: test_xsk: Split xskxceiver Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 02/15] selftests/bpf: test_xsk: Initialize bitmap before use Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 03/15] selftests/bpf: test_xsk: Fix __testapp_validate_traffic()'s return value Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 04/15] selftests/bpf: test_xsk: fix memory leak in testapp_stats_rx_dropped() Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 05/15] selftests/bpf: test_xsk: fix memory leak in testapp_xdp_shared_umem() Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 06/15] selftests/bpf: test_xsk: Wrap test clean-up in functions Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 07/15] selftests/bpf: test_xsk: Release resources when swap fails Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 08/15] selftests/bpf: test_xsk: Add return value to init_iface() Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 09/15] selftests/bpf: test_xsk: Don't exit immediately when xsk_attach fails Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 10/15] selftests/bpf: test_xsk: Don't exit immediately when gettimeofday fails Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 11/15] selftests/bpf: test_xsk: Don't exit immediately when workers fail Bastien Curutchet (eBPF Foundation)
2025-10-29 14:25   ` bot+bpf-ci [this message]
2025-10-29 13:52 ` [PATCH bpf-next v6 12/15] selftests/bpf: test_xsk: Don't exit immediately if validate_traffic fails Bastien Curutchet (eBPF Foundation)
2025-10-29 14:25   ` bot+bpf-ci
2025-10-29 13:52 ` [PATCH bpf-next v6 13/15] selftests/bpf: test_xsk: Don't exit immediately on allocation failures Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 14/15] selftests/bpf: test_xsk: Isolate non-CI tests Bastien Curutchet (eBPF Foundation)
2025-10-29 13:52 ` [PATCH bpf-next v6 15/15] selftests/bpf: test_xsk: Integrate test_xsk.c to test_progs framework Bastien Curutchet (eBPF Foundation)
2025-10-29 18:54 ` [PATCH bpf-next v6 00/15] selftests/bpf: " Alexei Starovoitov
2025-10-30  8:05   ` Bastien Curutchet

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=5c1c4101d42cc486366273556492d9be559f521d16629bbcd6b3adc6a4b746f0@mail.kernel.org \
    --to=bot+bpf-ci@kernel.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bastien.curutchet@bootlin.com \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jonathan.lemon@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --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

all inboxes | Powered by JetHome®