Reminder: 5 open syzbot bugs in "net/smc" subsystem
From: Eric Biggers
Date: Tue Jul 23 2019 - 22:29:39 EST
[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 5 of them as possibly being bugs in the "net/smc" 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 5 bugs, 4 were seen in mainline in the last week.
Of these 5 bugs, 1 was bisected to a commit from the following person:
Ursula Braun <ubraun@xxxxxxxxxxxxx>
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 "net/smc" subsystem, please let me
know, and if possible forward the report to the correct people or mailing list.
Here are the bugs:
--------------------------------------------------------------------------------
Title: WARNING in smc_unhash_sk (2)
Last occurred: 0 days ago
Reported: 101 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=f650845a184aed6947c0dd0f4d99d561335a7c31
Original thread: https://lkml.kernel.org/lkml/000000000000ac48ed05866bbc2c@xxxxxxxxxx/T/#u
This bug has a C reproducer.
This bug was bisected to:
commit 50717a37db032ce783f50685a73bb2ac68471a5a
Author: Ursula Braun <ubraun@xxxxxxxxxxxxx>
Date: Fri Apr 12 10:57:23 2019 +0000
net/smc: nonblocking connect rework
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+bd8cc73d665590a1fcad@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/000000000000ac48ed05866bbc2c@xxxxxxxxxx
--------------------------------------------------------------------------------
Title: WARNING: ODEBUG bug in __sk_destruct
Last occurred: 0 days ago
Reported: 450 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=591666b46bf0d9e2fbb8dbb386982d12ba804648
Original thread: https://lkml.kernel.org/lkml/000000000000451f9d056aff4397@xxxxxxxxxx/T/#u
This bug has a C reproducer.
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+92209502e7aab127c75f@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/000000000000451f9d056aff4397@xxxxxxxxxx
--------------------------------------------------------------------------------
Title: memory leak in new_inode_pseudo (2)
Last occurred: 1 day ago
Reported: 7 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=911dac8eb1de0c09979e8e0054cb6cbe198cd5bb
Original thread: https://lkml.kernel.org/lkml/000000000000111cbe058dc7754d@xxxxxxxxxx/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+e682cca30bc101a4d9d9@xxxxxxxxxxxxxxxxxxxxxxxxx
If you send any email or patch for this bug, please reply 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/000000000000111cbe058dc7754d@xxxxxxxxxx
--------------------------------------------------------------------------------
Title: WARNING in debug_check_no_obj_freed
Last occurred: 0 days ago
Reported: 33 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=83687867d4a435fce7c6045b34425b1cfb3bf2d6
Original thread: https://lkml.kernel.org/lkml/00000000000090ae7a058bc12946@xxxxxxxxxx/T/#u
This bug has a C reproducer.
syzbot has bisected this bug, but I think the bisection result is incorrect.
No one has replied to the original thread for this bug yet.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+b972214bb803a343f4fe@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/00000000000090ae7a058bc12946@xxxxxxxxxx
--------------------------------------------------------------------------------
Title: BUG: workqueue leaked lock or atomic in smc_tx_work
Last occurred: 27 days ago
Reported: 29 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=dd71ec2acfdd198626ec8e914f70afc70cf35c72
Original thread: https://lkml.kernel.org/lkml/0000000000006a28b5058c0d7e17@xxxxxxxxxx/T/#u
Unfortunately, this bug does not have a reproducer.
No one has replied to the original thread for this bug yet.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+8759e3927fd85a7c520a@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/0000000000006a28b5058c0d7e17@xxxxxxxxxx