From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: bot+bpf-ci@kernel.org, chenhuacai@kernel.org, hengqi.chen@gmail.com
Cc: loongarch@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org, eddyz87@gmail.com,
yonghong.song@linux.dev, mason@kernel.org,
ihor.solodrai@linux.dev
Subject: Re: [PATCH v1 2/2] LoongArch: BPF: Use beqz and bnez instructions for trampoline
Date: Tue, 3 Nov 2026 10:27:39 +0800 [thread overview]
Message-ID: <1276eb14-b851-aee7-36ad-d61e2ddd9ba4@loongson.cn> (raw)
In-Reply-To: <c3b8e6ae47164ab1a643a1730f0600993de03c8a30e35122a9812ac73d807697@mail.kernel.org>
On 2026/11/2 下午3:53, bot+bpf-ci@kernel.org wrote:
>> LoongArch: BPF: Use beqz and bnez instructions for trampoline
>
> TL;DR: Commit message only: the claimed branch-overflow risk looks impossible,
> since trampolines fit in one page and the old code behaved identically, so the
> Fixes: and Cc: stable tags may not be justified.
...
> Could the changelog drop the overflow-risk wording, or describe the change
> as a cleanup, and could the Fixes: and Cc: stable tags be reconsidered given
> that stable-kernel-rules requires a fix for a real bug?
Will update the commit message and remove the 'Fixes' and 'Cc: stable'
tags. If no more comments, I will send out v2 next week.
Thanks,
Tiezhu
next prev parent reply other threads:[~2026-11-03 2:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 7:28 [PATCH v1 0/2] LoongArch: BPF: Fix arena and trampoline Tiezhu Yang
2026-11-02 7:28 ` [PATCH v1 1/2] LoongArch: BPF: Make arena support depend on SCQ extension Tiezhu Yang
2026-11-02 14:20 ` Huacai Chen
2026-11-03 2:24 ` Tiezhu Yang
2026-11-04 4:29 ` Huacai Chen
2026-11-04 6:58 ` Tiezhu Yang
2026-11-04 9:54 ` Huacai Chen
2026-11-04 13:06 ` Tiezhu Yang
2026-11-05 2:24 ` Tiezhu Yang
2026-11-04 10:17 ` George Guo
2026-11-05 1:50 ` Tiezhu Yang
2026-11-02 7:28 ` [PATCH v1 2/2] LoongArch: BPF: Use beqz and bnez instructions for trampoline Tiezhu Yang
2026-11-02 7:53 ` bot+bpf-ci
2026-11-03 2:27 ` Tiezhu Yang [this message]
2026-11-06 14:45 ` Huacai Chen
2026-11-07 2:16 ` Tiezhu Yang
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=1276eb14-b851-aee7-36ad-d61e2ddd9ba4@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hengqi.chen@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=martin.lau@kernel.org \
--cc=mason@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
all inboxes | Powered by JetHome®