[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <484ca75b-d5f0-31db-6f81-2fb17ce0702e@linux.dev>
Date: Wed, 1 Feb 2023 09:46:36 -0800
From: Martin KaFai Lau <martin.lau@...ux.dev>
To: Jesper Dangaard Brouer <brouer@...hat.com>,
Stanislav Fomichev <sdf@...gle.com>
Cc: netdev@...r.kernel.org, martin.lau@...nel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, song@...nel.org,
yhs@...com, john.fastabend@...il.com, dsahern@...il.com,
willemb@...gle.com, void@...ifault.com, kuba@...nel.org,
xdp-hints@...-project.net, bpf@...r.kernel.org
Subject: Re: [PATCH bpf-next V2 2/4] selftests/bpf: xdp_hw_metadata cleanup
cause segfault
On 2/1/23 9:31 AM, Jesper Dangaard Brouer wrote:
> diff --git a/tools/testing/selftests/bpf/xdp_hw_metadata.c b/tools/testing/selftests/bpf/xdp_hw_metadata.c
> index 3823b1c499cc..438083e34cce 100644
> --- a/tools/testing/selftests/bpf/xdp_hw_metadata.c
> +++ b/tools/testing/selftests/bpf/xdp_hw_metadata.c
> @@ -121,7 +121,7 @@ static void close_xsk(struct xsk *xsk)
> xsk_umem__delete(xsk->umem);
> if (xsk->socket)
> xsk_socket__delete(xsk->socket);
> - munmap(xsk->umem, UMEM_SIZE);
> + munmap(xsk->umem_area, UMEM_SIZE);
Ah. Good catch. This should also explain a similar issue that CI is seeing in
the prog_tests/xdp_metadata.c.
Powered by blists - more mailing lists