Reminder: 3 open syzbot bugs in "net/ax25" subsystem
[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 3 of them as possibly being bugs in the "net/ax25" 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. 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/ax25" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: general protection fault in ax25_send_frame Last occurred: 0 days ago Reported: 204 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=1cdd5b120f129364fc8e9b2b027826cf99fa696e Original thread: https://lkml.kernel.org/lkml/9ea37c057e58d...@google.com/T/#u Unfortunately, this bug does not have a 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+e0b81535a27b8be39...@syzkaller.appspotmail.com 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/9ea37c057e58d...@google.com Title: KASAN: stack-out-of-bounds Write in ax25_getname Last occurred: 90 days ago Reported: 206 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=fb195f91dc044978c1b186f1288b1eff61edcc20 Original thread: https://lkml.kernel.org/lkml/ed4120057e2df...@google.com/T/#u This bug has a syzkaller reproducer only. 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+6a29097222b4d3b86...@syzkaller.appspotmail.com 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/ed4120057e2df...@google.com Title: inconsistent lock state in ax25_std_heartbeat_expiry Last occurred: 122 days ago Reported: 120 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=9086a8eac930890b2730d6441093bd478e32913f Original thread: https://lkml.kernel.org/lkml/1b07250584efb...@google.com/T/#u Unfortunately, this bug does not have a reproducer. The original thread for this bug received 2 replies; the last was 119 days ago. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+e350b81e95a6a214d...@syzkaller.appspotmail.com 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/1b07250584efb...@google.com
Reminder: 3 open syzbot bugs in "net/rose" subsystem
[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 3 of them as possibly being bugs in the "net/rose" 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 3 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 "net/rose" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: general protection fault in rose_send_frame Last occurred: 2 days ago Reported: 194 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=f46c94afb217ab49c75350adbd467d86ae2b59a6 Original thread: https://lkml.kernel.org/lkml/89904d057f1e0...@google.com/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+7078ae989d857fe17...@syzkaller.appspotmail.com 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/89904d057f1e0...@google.com Title: INFO: rcu detected stall in rose_loopback_timer (2) Last occurred: 46 days ago Reported: 44 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=42c06438fe5956ab9978486a1898ca2f23b1fc1f Original thread: https://lkml.kernel.org/lkml/cf98fa058adf3...@google.com/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+d37efb0ca1b826823...@syzkaller.appspotmail.com 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/cf98fa058adf3...@google.com Title: INFO: rcu detected stall in rose_connect Last occurred: 52 days ago Reported: 49 days ago Branches: net-next Dashboard link: https://syzkaller.appspot.com/bug?id=0b258dc8ece5bb93dfb5a137ae25a6db300d5892 Original thread: https://lkml.kernel.org/lkml/17b026058a785...@google.com/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+af81c7a21a31b18be...@syzkaller.appspotmail.com 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/17b026058a785...@google.com
Reminder: 13 open syzbot bugs in "net/netrom" subsystem
[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 13 of them as possibly being bugs in the "net/netrom" 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 13 bugs, 8 were seen in mainline in the last week. Of these 13 bugs, 4 were bisected to commits from the following person: Cong Wang 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/netrom" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: KASAN: use-after-free Read in nr_insert_socket Last occurred: 0 days ago Reported: 5 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=44bc727f1e55f249c97e876dd9163484c889b3ad Original thread: https://lkml.kernel.org/lkml/35f65d058df39...@google.com/T/#u This bug has a C reproducer. This bug was bisected to: commit c8c8218ec5af5d2598381883acbefbf604e56b5e Author: Cong Wang Date: Thu Jun 27 21:30:58 2019 + netrom: fix a memory leak in nr_rx_frame() The original thread for this bug has received 1 reply, 5 days ago. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+9399c158fcc09b21d...@syzkaller.appspotmail.com If you send any email or patch for this bug, please reply to the original thread, which had activity only 5 days ago. 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/35f65d058df39...@google.com Title: WARNING: refcount bug in nr_rx_frame Last occurred: 0 days ago Reported: 5 days ago Branches: Mainline Dashboard link: https://syzkaller.appspot.com/bug?id=4ffee6ac0fb5068b34959147b4d492bad89e98ab Original thread: https://lkml.kernel.org/lkml/222512058df13...@google.com/T/#u This bug has a C reproducer. This bug was bisected to: commit c8c8218ec5af5d2598381883acbefbf604e56b5e Author: Cong Wang Date: Thu Jun 27 21:30:58 2019 + netrom: fix a memory leak in nr_rx_frame() 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+622bdabb128acc334...@syzkaller.appspotmail.com 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/222512058df13...@google.com Title: KASAN: use-after-free Read in lock_sock_nested Last occurred: 3 days ago Reported: 202 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=6c137905024f86513297b035845acecb55fa9dab Original thread: https://lkml.kernel.org/lkml/7a5aad057e774...@google.com/T/#u This bug has a syzkaller reproducer only. 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+500c69d1e21d970e4...@syzkaller.appspotmail.com 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/7a5aad057e774...@google.com Title: memory leak in nr_create Last occurred: 1 day ago Reported: 57 days ago Branches: Mainline Dashboard link: https://syzkaller.appspot.com/bug?id=24be997a573ef9d497d6d7302518779b75d8119a Original thread: https://lkml.kernel.org/lkml/9412c60589e80...@google.com/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+10f1194569953b72f...@syzkaller.appspotmail.com If you send any
Reminder: 7 open syzbot bugs in "net/netrom" subsystem
[This email was generated by a script. Let me know if you have any suggestions to make it better.] Of the currently open syzbot reports against the upstream kernel, I've manually marked 7 of them as possibly being bugs in the "net/netrom" 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 7 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 "net/netrom" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: general protection fault in prepare_to_wait Last occurred: 1 day ago Reported: 174 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=c670fb9da2ce08f7b5101baa9426083b39ee9f90 Original thread: https://lkml.kernel.org/lkml/fa6a2c057e8b7...@google.com/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+55f9d3e51d49e20b2...@syzkaller.appspotmail.com 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/fa6a2c057e8b7...@google.com Title: memory leak in nr_create Last occurred: 7 days ago Reported: 30 days ago Branches: Mainline Dashboard link: https://syzkaller.appspot.com/bug?id=24be997a573ef9d497d6d7302518779b75d8119a Original thread: https://lkml.kernel.org/lkml/9412c60589e80...@google.com/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+10f1194569953b72f...@syzkaller.appspotmail.com 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/9412c60589e80...@google.com Title: memory leak in nr_rx_frame Last occurred: 30 days ago Reported: 30 days ago Branches: Mainline Dashboard link: https://syzkaller.appspot.com/bug?id=0c00cc3e04fe00ad69ac62fbe8464b2f0fae932a Original thread: https://lkml.kernel.org/lkml/da88840589e8f...@google.com/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+d6636a36d3c34bd88...@syzkaller.appspotmail.com 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/da88840589e8f...@google.com Title: KASAN: use-after-free Read in lock_sock_nested Last occurred: 24 days ago Reported: 175 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=6c137905024f86513297b035845acecb55fa9dab Original thread: https://lkml.kernel.org/lkml/7a5aad057e774...@google.com/T/#u This bug has a syzkaller reproducer only. 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+500c69d1e21d970e4...@syzkaller.appspotmail.com 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/7a5aad057e774...@google.com Title: KASAN: use-after-free Read in nr_release Last occurred: 0 days ago Reported: 18 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=5332f4a9ce674d6378f0bd91af752d2be80f3aba Origi
Reminder: 4 open syzbot bugs in "net/ax25" subsystem
[This email was generated by a script. Let me know if you have any suggestions to make it better.] Of the currently open syzbot reports against the upstream kernel, I've manually marked 4 of them as possibly being bugs in the "net/ax25" 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. 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/ax25" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: general protection fault in ax25_send_frame Last occurred: 0 days ago Reported: 177 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=1cdd5b120f129364fc8e9b2b027826cf99fa696e Original thread: https://lkml.kernel.org/lkml/9ea37c057e58d...@google.com/T/#u Unfortunately, this bug does not have a 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+e0b81535a27b8be39...@syzkaller.appspotmail.com 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/9ea37c057e58d...@google.com Title: KASAN: stack-out-of-bounds Write in ax25_getname Last occurred: 63 days ago Reported: 179 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=fb195f91dc044978c1b186f1288b1eff61edcc20 Original thread: https://lkml.kernel.org/lkml/ed4120057e2df...@google.com/T/#u This bug has a syzkaller reproducer only. 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+6a29097222b4d3b86...@syzkaller.appspotmail.com 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/ed4120057e2df...@google.com Title: inconsistent lock state in ax25_std_heartbeat_expiry Last occurred: 95 days ago Reported: 93 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=9086a8eac930890b2730d6441093bd478e32913f Original thread: https://lkml.kernel.org/lkml/1b07250584efb...@google.com/T/#u Unfortunately, this bug does not have a reproducer. The original thread for this bug received 2 replies; the last was 92 days ago. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+e350b81e95a6a214d...@syzkaller.appspotmail.com 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/1b07250584efb...@google.com Title: general protection fault in ax25_send_control Last occurred: 170 days ago Reported: 169 days ago Branches: net-next Dashboard link: https://syzkaller.appspot.com/bug?id=bacca5f8fe81f2486fb73fd9e130a3035dc46594 Original thread: https://lkml.kernel.org/lkml/77264c057eec9...@google.com/T/#u Unfortunately, this bug does not have a 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+d0b03d6dbe11a950e...@syzkaller.appspotmail.com 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/77264c057eec9...@google.com
Reminder: 3 open syzbot bugs in "net/rose" subsystem
[This email was generated by a script. Let me know if you have any suggestions to make it better.] Of the currently open syzbot reports against the upstream kernel, I've manually marked 3 of them as possibly being bugs in the "net/rose" 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. 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/rose" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: Title: general protection fault in rose_send_frame Last occurred: 0 days ago Reported: 167 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=f46c94afb217ab49c75350adbd467d86ae2b59a6 Original thread: https://lkml.kernel.org/lkml/89904d057f1e0...@google.com/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+7078ae989d857fe17...@syzkaller.appspotmail.com 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/89904d057f1e0...@google.com Title: INFO: rcu detected stall in rose_loopback_timer (2) Last occurred: 19 days ago Reported: 17 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=42c06438fe5956ab9978486a1898ca2f23b1fc1f Original thread: https://lkml.kernel.org/lkml/cf98fa058adf3...@google.com/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+d37efb0ca1b826823...@syzkaller.appspotmail.com 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/cf98fa058adf3...@google.com Title: INFO: rcu detected stall in rose_connect Last occurred: 25 days ago Reported: 22 days ago Branches: net-next Dashboard link: https://syzkaller.appspot.com/bug?id=0b258dc8ece5bb93dfb5a137ae25a6db300d5892 Original thread: https://lkml.kernel.org/lkml/17b026058a785...@google.com/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+af81c7a21a31b18be...@syzkaller.appspotmail.com 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/17b026058a785...@google.com
