All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qiliang Yuan <odys.yuan@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
	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,
	luis.gerhorst@fau.de, henriette.herzog@rub.de,
	a.s.protopopov@gmail.com, xukuohai@huawei.com,
	hengqi.chen@gmail.com, shuah@kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/5] bpf: Fix three bugs around constant blinding and nop removal
Date: Wed, 04 Nov 2026 04:40:09 +0000	[thread overview]
Message-ID: <179376720904.2078713.14897677456982144973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102-bpf-blind-nops-fixes-v1-0-844300e42cdb@gmail.com>

Hello:

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

On Mon, 02 Nov 2026 07:37:00 -0500 you wrote:
> Alexei listed three bugs that were in the tree before the patch list
> series [1]. Each patch fixes one, the last two add tests:
> 
>   bug                                                  fix   test
>   line info stays blinded when the JIT falls back      1     -
>   removing a nospec jump as a nop drops its barrier    2     4
>   log_true_size misses an error from blinding          3     5
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/5] bpf: Put the line info back when the JIT falls back after blinding
    https://git.kernel.org/bpf/bpf-next/c/82e89a32c974
  - [bpf-next,2/5] bpf: Keep the barrier of a nospec insn when removing nops
    https://git.kernel.org/bpf/bpf-next/c/ea2ae2cdadee
  - [bpf-next,3/5] bpf: Finalize the verifier log after the runtime is selected
    https://git.kernel.org/bpf/bpf-next/c/4dc6335da407
  - [bpf-next,4/5] selftests/bpf: Cover a nospec jump that becomes a nop
    https://git.kernel.org/bpf/bpf-next/c/08843010ceae
  - [bpf-next,5/5] selftests/bpf: Test log_true_size with an error from blinding
    https://git.kernel.org/bpf/bpf-next/c/970c0d366166

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



      parent reply	other threads:[~2026-11-04  4:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 12:37 [PATCH bpf-next 0/5] bpf: Fix three bugs around constant blinding and nop removal Qiliang Yuan
2026-11-02 12:37 ` [PATCH bpf-next 1/5] bpf: Put the line info back when the JIT falls back after blinding Qiliang Yuan
2026-11-02 12:37 ` [PATCH bpf-next 2/5] bpf: Keep the barrier of a nospec insn when removing nops Qiliang Yuan
2026-11-02 12:37 ` [PATCH bpf-next 3/5] bpf: Finalize the verifier log after the runtime is selected Qiliang Yuan
2026-11-03 12:58   ` Xu Kuohai
2026-11-02 12:37 ` [PATCH bpf-next 4/5] selftests/bpf: Cover a nospec jump that becomes a nop Qiliang Yuan
2026-11-02 12:37 ` [PATCH bpf-next 5/5] selftests/bpf: Test log_true_size with an error from blinding Qiliang Yuan
2026-11-02 12:45   ` sashiko-bot
2026-11-04  4:40 ` 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=179376720904.2078713.14897677456982144973.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=a.s.protopopov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=hengqi.chen@gmail.com \
    --cc=henriette.herzog@rub.de \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luis.gerhorst@fau.de \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=odys.yuan@gmail.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xukuohai@huawei.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 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.