[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAN+4W8j5qe6p3YV90g-E0VhV7AmYyAvt0z50dfDSombbGghkww@mail.gmail.com>
Date: Tue, 11 Apr 2023 16:08:32 +0100
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 Tue, Mar 28, 2023 at 11:18 AM Lorenz Bauer <lmb@...valent.com> wrote:
>
> On Mon, Mar 20, 2023 at 3:48 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> >
> > Why would it break? Is that because the test is buggy, or the kernel is
> > buggy?
>
> This test will be fine, but there have been several times when
> selftests/bpf for stable kernel releases didn't actually compile due
> to backported tests. This is because macros we're redefined, etc.
> Unless those also get picked (seems like a sisyphean task) we'll keep
> seeing broken selftests/bpf on stable.
Hi Greg, Sasha,
Following up on this since it seems to have fallen through the cracks.
Lorenz
Powered by blists - more mailing lists