From: Paul Chaignon <paul.chaignon@gmail.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Emil Tsalapatis <emil@etsalapatis.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Hengqi Chen <hengqi.chen@gmail.com>,
loongarch@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1 1/2] selftests/bpf: Check alignment flag if expected result is REJECT
Date: Mon, 16 Mar 2026 14:04:48 +0100 [thread overview]
Message-ID: <abf_8FcnQr50CCTn@mail.gmail.com> (raw)
In-Reply-To: <7ea56716-fd5f-1740-e634-1dec4196dd2c@loongson.cn>
On Thu, Mar 12, 2026 at 07:06:38PM +0800, Tiezhu Yang wrote:
> On 03/12/2026 05:29 PM, Paul Chaignon wrote:
> > On Thu, Mar 12, 2026 at 02:59:57PM +0800, Tiezhu Yang wrote:
[...]
> > > -#14/p Dest pointer in r0 - succeed, check 5 OK
> > > +#14/p Dest pointer in r0 - succeed, check 5 OK (NOTE: not executed due to
> > > unknown alignment)
> >
> > As stated in my previous answer, this note would be incorrect: the
> > program was executed in test case #14 because it was rejected, not
> > because of unknown alignment.
>
> OK, please ignore this patch.
I think the second patch in this set is still worthwhile, so maybe
resend it on its own?
Paul
>
> Thanks,
> Tiezhu
>
next prev parent reply other threads:[~2026-03-16 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:45 [PATCH bpf-next v1 0/2] Modify some code about test_verifier Tiezhu Yang
2026-03-10 6:45 ` [PATCH bpf-next v1 1/2] selftests/bpf: Check alignment flag if expected result is REJECT Tiezhu Yang
2026-03-11 15:56 ` Emil Tsalapatis
2026-03-12 6:59 ` Tiezhu Yang
2026-03-12 9:29 ` Paul Chaignon
2026-03-12 11:06 ` Tiezhu Yang
2026-03-16 13:04 ` Paul Chaignon [this message]
2026-03-17 1:56 ` Tiezhu Yang
2026-03-11 16:11 ` Paul Chaignon
2026-03-10 6:45 ` [PATCH bpf-next v1 2/2] selftests/bpf: Add alignment flag for test_verifier 190 testcase Tiezhu Yang
2026-03-11 15:57 ` Emil Tsalapatis
2026-03-11 16:13 ` Paul Chaignon
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=abf_8FcnQr50CCTn@mail.gmail.com \
--to=paul.chaignon@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=emil@etsalapatis.com \
--cc=hengqi.chen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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