[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAN+4W8jn2P9LtB=4FtWxFikmEdGGbaxBvUg7swkip+EzqfzHPg@mail.gmail.com>
Date: Tue, 30 May 2023 13:24:28 +0200
From: Lorenz Bauer <lmb@...valent.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Martin KaFai Lau <martin.lau@...nel.org>,
ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
shuah@...nel.org, yhs@...com, eddyz87@...il.com, sdf@...gle.com,
error27@...il.com, iii@...ux.ibm.com, memxor@...il.com,
bpf@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.2 08/30] selftests/bpf: check that modifier
resolves after pointer
On Fri, May 26, 2023 at 6:43 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> So what tree(s) does this need to be backported to? I'm confused, this
> is a 6.2 email thread which is long end-of-life.
That would be 5.10 from what I can tell. Other LTS kernels have
working tools/testing/selftests/bpf.
I replied here because you asked for examples :)
> It can be avoided by people testing and letting me know when things
> break :)
Fair enough. Earlier you said:
> And selftests should NOT be broken on stable releases, if so, something
> is wrong as no other subsystem has that happen.
Why is bpf special in this regard then?
Best
Lorenz
Powered by blists - more mailing lists