All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v4 0/4] selftests/bpf: Fix a few test failures with arm64 64KB page
Date: Sat, 07 Jun 2025 02:30:34 +0000	[thread overview]
Message-ID: <174926343400.4065959.16518552978353161599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250607013605.1550284-1-yonghong.song@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri,  6 Jun 2025 18:36:05 -0700 you wrote:
> My local arm64 host has 64KB page size and the VM to run test_progs
> also has 64KB page size. There are a few self tests assuming 4KB page
> and failed in my environment.
> 
> Patch 1 reduced long assert logs so if the test fails, developers
> can check logs easily. Patches 2-4 fixed three selftest failures.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/4] selftests/bpf: Reduce test_xdp_adjust_frags_tail_grow logs
    https://git.kernel.org/bpf/bpf-next/c/ae8824037a0a
  - [bpf-next,v4,2/4] selftests/bpf: Fix bpf_mod_race test failure with arm64 64KB page size
    https://git.kernel.org/bpf/bpf-next/c/377d3715900c
  - [bpf-next,v4,3/4] selftests/bpf: Fix ringbuf/ringbuf_write test failure with arm64 64KB page size
    https://git.kernel.org/bpf/bpf-next/c/8c8c5e3c854a
  - [bpf-next,v4,4/4] selftests/bpf: Fix a user_ringbuf failure with arm64 64KB page size
    https://git.kernel.org/bpf/bpf-next/c/bbc7bd658ddc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-06-07  2:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  1:36 [PATCH bpf-next v4 0/4] selftests/bpf: Fix a few test failures with arm64 64KB page Yonghong Song
2025-06-07  1:36 ` [PATCH bpf-next v4 1/4] selftests/bpf: Reduce test_xdp_adjust_frags_tail_grow logs Yonghong Song
2025-06-07  1:36 ` [PATCH bpf-next v4 2/4] selftests/bpf: Fix bpf_mod_race test failure with arm64 64KB page size Yonghong Song
2025-06-07  1:36 ` [PATCH bpf-next v4 3/4] selftests/bpf: Fix ringbuf/ringbuf_write " Yonghong Song
2025-06-07  1:36 ` [PATCH bpf-next v4 4/4] selftests/bpf: Fix a user_ringbuf " Yonghong Song
2025-06-07  2:30 ` patchwork-bot+netdevbpf [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=174926343400.4065959.16518552978353161599.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@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.