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, Stefano
