[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250424-imported-beautiful-orangutan-bb09e0@meerkat>
Date: Thu, 24 Apr 2025 14:51:51 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: patchwork-bot+netdevbpf@...nel.org, Jakub Kicinski <kuba@...nel.org>,
Ilya Leoshkevich <iii@...ux.ibm.com>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>, bpf <bpf@...r.kernel.org>,
Heiko Carstens <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>, Network Development <netdev@...r.kernel.org>
Subject: Re: [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock
On Thu, Apr 24, 2025 at 11:41:16AM -0700, Alexei Starovoitov wrote:
> On Thu, Apr 24, 2025 at 11:32 AM <patchwork-bot+netdevbpf@...nel.org> wrote:
> >
> > Hello:
> >
> > This series was applied to netdev/net-next.git (main)
> > by Jakub Kicinski <kuba@...nel.org>:
> >
> > On Thu, 24 Apr 2025 18:41:24 +0200 you wrote:
> > > Hi,
> > >
> > > I tried running the arena_spin_lock test on s390x and ran into the
> > > following issues:
> > >
> > > * Changing the header file does not lead to rebuilding the test.
> > > * The checked for number of CPUs and the actually required number of
> > > CPUs are different.
> > > * Endianness issue in spinlock definition.
> > >
> > > [...]
> >
> > Here is the summary with links:
> > - [1/3] selftests/bpf: Fix arena_spin_lock.c build dependency
> > https://git.kernel.org/netdev/net-next/c/4fe09ff1a54a
> > - [2/3] selftests/bpf: Fix arena_spin_lock on systems with less than 16 CPUs
> > (no matching commit)
> > - [3/3] selftests/bpf: Fix endianness issue in __qspinlock declaration
> > (no matching commit)
>
> Hmm. Looks like pw-bot had too much influence from AI bots
> and started hallucinating itself :)
I'll look into what happened here.
-K
Powered by blists - more mailing lists