Re: Policy regarding linux-next only changes

[Alexander Potapenko]

On Mon, Jul 20, 2026 at 12:06 PM Tetsuo Handa
<penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote:
>
> On 2026/07/04 21:06, Miguel Ojeda wrote:
> > I understand it may be nice to use such resources, but the solution is
> > to talk to both sides, as you do in that thread. From what I see, they
> > even offered to add a mailing list for those patches:
> >
> >   "Aleksandr says we can create a special mailing list to test draft
> >   patches, so the series sent to that list is fuzzed for some time,
> >   similarly to how upstream patch testing works now.
> >   Do you think that would help you to debug these issues? "
> >
> > So what happened with that? It seems there was a way forward there,
> > no? (Cc'ing Alexander from that thread)
>
> Alexander, was there any progress?
>

Hi Tetsuo,

You can send patches to syzbot@xxxxxxxxxxxxxxx.

E.g. I ran

$ git send-email  --suppress-cc=all --to=syzbot@xxxxxxxxxxxxxxx
patches/kcov-tetsuo-v7/0001-kcov-fix-data-corruption-and-race-conditions-on-PREE.patch

to test your latest kcov patch and got the results here:
https://ci.syzbot.org/series/33930a89-bb2a-4c5a-b6c5-d45829d5c94c

The fuzzing ran on 8 VMs for 3 hours, and there were no new reports.

Please let us know what you think of this workflow.