Re: Policy regarding linux-next only changes

On Wed, Jul 29, 2026 at 1:46=E2=80=AFAM Tetsuo Handa
<[email protected]> wrote:
>
> syzbot uses kernel.panic_on_warn=3D1, for most of WARN*() users are repor=
ting
> problems that should not be ignored. Therefore, WARN*() must not be used =
for
> reporting recoverable mistakes like -EINVAL. Abusing WARN*() like
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/=
kernel/workqueue.c?id=3D6e845bcb78c95af935094040bd4edc3c2b6dd784#n5855
> is a fatal barrier for continuous testing systems like syzbot.

Yeah, a lot of CIs that grep for certain keywords in the kernel log
(or that simply enable the panicking) suffer from those, but the idea
I was mentioning is to defer that until the fuzzing starts -- see
Ted's reply, it sounds potentially doable.

It may not solve the complete problem, but it may allow you, for
certain trees or periods of time, to continue your testing. Thus
removing a bit of the coupling between you and other maintainers, i.e.
making life easier for both sides.

I don't know -- I am just trying to find compromises that could help you.

Cheers,
Miguel