BPF List
 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,
	hodgesd@meta.com
Subject: Re: [PATCH bpf-next v3 1/2] bpf, x64: Fix a jit convergence issue
Date: Thu, 05 Sep 2024 00:00:36 +0000	[thread overview]
Message-ID: <172549443601.1204284.9842696096405416322.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240904221251.37109-1-yonghong.song@linux.dev>

Hello:

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

On Wed,  4 Sep 2024 15:12:51 -0700 you wrote:
> Daniel Hodges reported a jit error when playing with a sched-ext program.
> The error message is:
>   unexpected jmp_cond padding: -4 bytes
> 
> But further investigation shows the error is actual due to failed
> convergence. The following are some analysis:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/2] bpf, x64: Fix a jit convergence issue
    https://git.kernel.org/bpf/bpf-next/c/c8831bdbfbab
  - [bpf-next,v3,2/2] selftests/bpf: Add a selftest for x86 jit convergence issues
    https://git.kernel.org/bpf/bpf-next/c/eff5b5fffc1d

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



      parent reply	other threads:[~2024-09-05  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 22:12 [PATCH bpf-next v3 1/2] bpf, x64: Fix a jit convergence issue Yonghong Song
2024-09-04 22:12 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add a selftest for x86 jit convergence issues Yonghong Song
2024-09-05  0:00 ` 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=172549443601.1204284.9842696096405416322.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=hodgesd@meta.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox