On Mon, Jul 6, 2026 at 1:32 PM 'mawupeng' via syzkaller-bugs <[email protected]> wrote: > > > > On 周一 2026-7-6 17:24, Stefano Garzarella wrote: > > On Thu, 2 Jul 2026 at 04:55, mawupeng <[email protected]> wrote: > >> On 周四 2026-6-25 04:32, syzbot wrote: > >>> Hello virt maintainers/developers, > >>> > >>> This is a 31-day syzbot report for the virt subsystem. > >>> All related reports/information can be found at: > >>> https://syzkaller.appspot.com/upstream/s/virt > >>> > >>> During the period, 0 new issues were detected and 0 were fixed. > >>> In total, 5 issues are still open and 61 have already been fixed. > >>> There are also 2 low-priority issues. > >>> > >>> Some of the still happening issues: > >>> > >>> Ref Crashes Repro Title > >>> <1> 24 No WARNING: refcount bug in call_timer_fn (4) > >>> > >>> https://syzkaller.appspot.com/bug?extid=07dcf509f4c013e25dc5 > >>> <2> 3 Yes memory leak in __vsock_create (2) > >>> > >>> https://syzkaller.appspot.com/bug?extid=1b2c9c4a0f8708082678 > >> > >> Hi, > >> > >> This is regarding the still-open "memory leak in __vsock_create (2)" > >> bug (#2 in the monthly virt report, extid 1b2c9c4a0f8708082678): > >> https://syzkaller.appspot.com/bug?extid=1b2c9c4a0f8708082678 > >> > >> I spent some time analyzing the root cause and the previous fix > >> attempt; below is a summary and a direction that tested out. > > > > [...] > > > >> > >> I'm not subscribed to follow the list at full volume; happy to send a > >> formal patch (with the af_vsock.h / pending_work changes folded in) > >> if the direction looks right to the maintainers. > > > > Yes, please, a formal patch with a great commit message is much better > > than a long text to read IMO. > > Thanks for replying. > > As we conducted more thorough testing and further analysis of our own fix, > we found that it is not as comprehensive as the existing AI-generated fix > provided[1]. > > Could you please let us know if there are any issues with this AI-generated > fix? > > [1]: > https://syzkaller.appspot.com/ai_job?id=cd978d21-2110-4f57-9525-d7d91c4a7e02
I'll chime in from the syzbot side. If anything is missing, please let us know :) Otherwise, please note that the bot can incorporate code review notes and, once the patch is ready, submit it to the LKML: https://github.com/google/syzkaller/blob/master/docs/syzbot_ai_patches.md Best Regards, Aleksandr > > > > > Thanks, > > Stefano > > > > >
