Re: Policy regarding linux-next only changes

[Tetsuo Handa]

On 2026/07/21 18:38, Alexander Potapenko wrote:
> 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.

Unfortunately, 8 VMs for 3 hours would be too little to stop my linux-next only patches.

syzbot took more than one month in linux-next until I was able to report
https://lkml.kernel.org/r/73ed3aa5-f6e1-47b6-9e5d-428ac1f4cbf3@xxxxxxxxxxxxxxxxxxx .
I could have reported within 24 hours if all VMs (I don't know how many VMs are assigned)
for networking trees were tested with my linux-next only patch.

syzbot was not able to trigger
"BUG: %s/%u is doing I/O request on loop%d in Lo_rundown state.\n" message
using https://lkml.kernel.org/r/30ccdd3c-6353-4a0f-bdc7-230ec3bf4765@xxxxxxxxxxxxxxxxxxx
in linux-next tree. syzbot could have triggered this message within 24 hours if all VMs
for upstream trees were tested with my linux-next only patch.

What I want is a workflow that can test with patches for many days and many VMs.