On Tue, 2 Jul 2019 13:30:07 +0800 Jason Wang wrote: > On 2019/7/2 Eric Biggers wrote: > > [This email was generated by a script. Let me know if you have any suggestions > > to make it better, or if you want it re-generated with the latest status.] > > > > Of the currently open syzbot reports against the upstream kernel, I've manually > > marked 2 of them as possibly being bugs in the vhost subsystem. I've listed > > these reports below, sorted by an algorithm that tries to list first the reports > > most likely to be still valid, important, and actionable. > > > > Of these 2 bugs, 1 was seen in mainline in the last week. > > > > If you believe a bug is no longer valid, please close the syzbot report by > > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the > > original thread, as explained at https://goo.gl/tpsmEJ#status > > > > If you believe I misattributed a bug to the vhost subsystem, please let me know, > > and if possible forward the report to the correct people or mailing list. > > > > Here are the bugs: > > > > -------------------------------------------------------------------------------- > > Title: memory leak in vhost_net_ioctl > > Last occurred: 0 days ago > > Reported: 26 days ago > > Branches: Mainline > > Dashboard link: https://syzkaller.appspot.com/bug?id=3D12ba349d7e26ccfe95317bc376e812ebbae2ee0f > > Original thread: https://lkml.kernel.org/lkml/000000000000188da1058a9c25e3@xxxxxxxxxx/T/#u > > > > This bug has a C reproducer. > > > > The original thread for this bug has received 4 replies; the last was 17 days > > ago. > > > > If you fix this bug, please add the following tag to the commit: > > Reported-by: syzbot+0789f0c7e45efd7bb643@xxxxxxxxxxxxxxxxxxxxxxxxx > > > > If you send any email or patch for this bug, please consider replying to the > > original thread. For the git send-email command to use, or tips on how to reply > > if the thread isn't in your mailbox, see the "Reply instructions" at > > https://lkml.kernel.org/r/000000000000188da1058a9c25e3@xxxxxxxxxx > > > Cc Hillf who should had a fix for this. > It could not be a fix in any form without the great idea you shared, Jason:) while reviewing the first version. > Hillf, would you please post a formal patch for this? (for -net) > And feel free to do this thing appropriate or that thing for fixing the reported memory leak before I can earn a Tested-by. -- Hillf _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
