* Reminder: 99 open syzbot bugs in net subsystem
@ 2019-07-24 1:38 Eric Biggers
2019-07-24 6:39 ` Eric Dumazet
0 siblings, 1 reply; 14+ messages in thread
From: Eric Biggers @ 2019-07-24 1:38 UTC (permalink / raw)
To: netdev, David S. Miller, Florian Westphal, Ilya Maximets,
Eric Dumazet, David Ahern
Cc: linux-kernel, syzkaller-bugs
[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 99 of them as possibly being bugs in the net subsystem. This category
only includes the networking bugs that I couldn't assign to a more specific
component (bpf, xfrm, bluetooth, tls, tipc, sctp, wireless, etc.). 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 99 bugs, 17 were seen in mainline in the last week.
Of these 99 bugs, 4 were bisected to commits from the following people:
Florian Westphal <fw@strlen.de>
Ilya Maximets <i.maximets@samsung.com>
Eric Dumazet <edumazet@google.com>
David Ahern <dsahern@gmail.com>
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 subsystem, please let me know,
and if possible forward the report to the correct people or mailing list.
Here are the bugs:
--------------------------------------------------------------------------------
Title: unregister_netdevice: waiting for DEV to become free (2)
Last occurred: 0 days ago
Reported: 342 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=bae9a2236bfede42cf3d219e6bf6740c583568a4
Original thread: https://lkml.kernel.org/lkml/00000000000056268e05737dcb95@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 27 replies; the last was 80 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+30209ea299c09d8785c9@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/00000000000056268e05737dcb95@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at net/core/skbuff.c:LINE! (3)
Last occurred: 1 day ago
Reported: 537 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=9c55af67ce995cf6c4f11ab6f5d3ee805d67fc00
Original thread: https://groups.google.com/d/msgid/syzkaller-bugs/001a114372a6074e6505642b7f72%40google.com
This bug has a C reproducer.
For some reason the original report email for this bug is missing from the LKML
archive at lore.kernel.org, so my script couldn't check whether anyone has
replied to it or not. The Google Groups link above should still work, though.
Also try searching for the bug title.
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in __netif_receive_skb_core
Last occurred: 0 days ago
Reported: 467 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=0c8e5c99b3db338c8956fcb7231eb1f7e2d707f9
Original thread: https://lkml.kernel.org/lkml/94eb2c059ce01f643c0569a228ee@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 3 replies; the last was 466 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+b202b7208664142954fa@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/94eb2c059ce01f643c0569a228ee@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in ip6_parse_tlv
Last occurred: 0 days ago
Reported: 306 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=a446d3718ee6322911a0c6d34db57909e1838fe7
Original thread: https://lkml.kernel.org/lkml/00000000000030779c057653b9ef@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+f08ac29f2ac8aea19826@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/00000000000030779c057653b9ef@google.com
--------------------------------------------------------------------------------
Title: WARNING in xt_compat_add_offset
Last occurred: 1 day ago
Reported: 151 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=28b6bf730a5e8d288db5c794d5c6ccc49f746d74
Original thread: https://lkml.kernel.org/lkml/00000000000081994205827ea9a0@google.com/T/#u
This bug has a C reproducer.
This bug was bisected to:
commit 2035f3ff8eaa29cfb5c8e2160b0f6e85eeb21a95
Author: Florian Westphal <fw@strlen.de>
Date: Mon Jan 21 20:54:36 2019 +0000
netfilter: ebtables: compat: un-break 32bit setsockopt when no rules are present
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+276ddebab3382bbf72db@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/00000000000081994205827ea9a0@google.com
--------------------------------------------------------------------------------
Title: WARNING in rollback_registered_many (2)
Last occurred: 0 days ago
Reported: 258 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=d39aca7a05a76d146ba96cddbb3242075d9171a7
Original thread: https://lkml.kernel.org/lkml/000000000000d9f094057a17b97b@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 1 reply, 102 days ago.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+40918e4d826fb2ff9b96@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/000000000000d9f094057a17b97b@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in bcmp
Last occurred: 0 days ago
Reported: 45 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=38933ca8abb1b8f0ee10c430f3a6c1f6a68a2519
Original thread: https://lkml.kernel.org/lkml/0000000000008f00f7058ad13ec8@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+d8b02c920ae8f3e0be75@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/0000000000008f00f7058ad13ec8@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in mii_nway_restart
Last occurred: 0 days ago
Reported: 49 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=835562bfa4dd92c72f323f29ad388c9cb4b0e63f
Original thread: https://lkml.kernel.org/lkml/000000000000f71859058a7cfdc8@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+1f53a30781af65d2c955@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/000000000000f71859058a7cfdc8@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in r871xu_drv_init
Last occurred: 2 days ago
Reported: 47 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=3cd92b1d85428b128503bfa7a250294c9ae00bd8
Original thread: https://lkml.kernel.org/lkml/000000000000417702058aa80506@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+6f5ecd144854c0d8580b@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/000000000000417702058aa80506@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in ax88178_bind
Last occurred: 1 day ago
Reported: 46 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=d601416c178e3d67888024bdf7774477a034840b
Original thread: https://lkml.kernel.org/lkml/000000000000cba2b6058ac09eeb@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+abd25d675d47f23f188c@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/000000000000cba2b6058ac09eeb@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in rtnl_lock (6)
Last occurred: 4 days ago
Reported: 15 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=5dcc2956e8737c91083930c55796c5b98750f1d2
Original thread: https://lkml.kernel.org/lkml/000000000000ba542e058d309136@google.com/T/#u
This bug has a C reproducer.
This bug was bisected to:
commit 455302d1c9ae9318660aaeb9748a01ff414c9741
Author: Ilya Maximets <i.maximets@samsung.com>
Date: Fri Jun 28 08:04:07 2019 +0000
xdp: fix hang while unregistering device bound to xdp socket
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+174ce29c2308dec5bc68@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/000000000000ba542e058d309136@google.com
--------------------------------------------------------------------------------
Title: INFO: task hung in unregister_netdevice_notifier (3)
Last occurred: 2 days ago
Reported: 156 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=1724d278c83ca6e6df100a2e320c10d991cf2bce
Original thread: https://lkml.kernel.org/lkml/0000000000009d787a0582128cbe@google.com/T/#u
This bug has a syzkaller reproducer only.
The original thread for this bug received 2 replies; the last was 8 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+0f1827363a305f74996f@syzkaller.appspotmail.com
If you send any email or patch for this bug, please reply to the original
thread, which had activity only 8 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/0000000000009d787a0582128cbe@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in gre_parse_header
Last occurred: 0 days ago
Reported: 30 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=af9d9384bbda6732044cf6335966df874a40cff1
Original thread: https://lkml.kernel.org/lkml/000000000000dc4531058bfb4605@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+f583ce3d4ddf9836b27a@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/000000000000dc4531058bfb4605@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in ila_nf_input
Last occurred: 1 day ago
Reported: 189 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=6911f9daa3f3c89b595884f30b212e60e889d384
Original thread: https://lkml.kernel.org/lkml/0000000000003036f4057f81e98e@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+03a25358f4cba0bc4cb6@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/0000000000003036f4057f81e98e@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in smsc95xx_read_eeprom (2)
Last occurred: 0 days ago
Reported: 13 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=0629febb76ae17ff78874aa68991e542506b1351
Original thread: https://lkml.kernel.org/lkml/000000000000e38991058d54c35f@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+0dfe788c0e7be7c95931@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/000000000000e38991058d54c35f@google.com
--------------------------------------------------------------------------------
Title: general protection fault in tcf_ife_init
Last occurred: 3 days ago
Reported: 1 day ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=ae313e1903160aebaac974b675db644baa44f581
Original thread: https://lkml.kernel.org/lkml/000000000000772876058e46063f@google.com/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+fbb5b288c9cb6a2eeac4@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/000000000000772876058e46063f@google.com
--------------------------------------------------------------------------------
Title: memory leak in kobject_set_name_vargs (2)
Last occurred: 1 day ago
Reported: 0 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=f5f4af9fb9ffb3112ad6e30f717f769decdccdfc
Original thread: https://lkml.kernel.org/lkml/000000000000edcb3c058e6143d5@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+ad8ca40ecd77896d51e2@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/000000000000edcb3c058e6143d5@google.com
--------------------------------------------------------------------------------
Title: WARNING in mcba_usb_probe/usb_submit_urb
Last occurred: 1 day ago
Reported: 13 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=6daf4bbae6c9c761ac2863d6d23be4cbdaebde7d
Original thread: https://lkml.kernel.org/lkml/000000000000996786058d52cb39@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+3bc1dce0cc0052d60fde@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/000000000000996786058d52cb39@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in usb_kill_anchored_urbs
Last occurred: 17 days ago
Reported: 42 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=18b605fd212e6e477e038c699430b44ca5946eac
Original thread: https://lkml.kernel.org/lkml/000000000000e84a3a058b0f9307@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+eb6ab607626fd1dac0f1@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/000000000000e84a3a058b0f9307@google.com
--------------------------------------------------------------------------------
Title: memory leak in __nf_hook_entries_try_shrink
Last occurred: 16 days ago
Reported: 40 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=a00ae6ea26b62609c1df4d7f0d21e4a7635d8203
Original thread: https://lkml.kernel.org/lkml/0000000000005718ef058b3a0fcf@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+c51f73e78e7e2ce3a31e@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/0000000000005718ef058b3a0fcf@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in do_ip_vs_set_ctl
Last occurred: 29 days ago
Reported: 312 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=46ebfb92a8a812621a001ef04d90dfa459520fe2
Original thread: https://lkml.kernel.org/lkml/00000000000015a13b0575d8eae8@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+23b5f9e7caf61d9a3898@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/00000000000015a13b0575d8eae8@google.com
--------------------------------------------------------------------------------
Title: kernel panic: stack is corrupted in __lock_acquire (4)
Last occurred: 5 days ago
Reported: 43 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=b75c6f861ac07fc8410957c22e74802b4313ec3d
Original thread: https://lkml.kernel.org/lkml/0000000000009b3b80058af452ae@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+83979935eb6304f8cd46@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/0000000000009b3b80058af452ae@google.com
--------------------------------------------------------------------------------
Title: memory leak in fdb_create
Last occurred: 29 days ago
Reported: 29 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=7ca7d71ade3608a7f92ac4b8c9c499cf130e68a9
Original thread: https://lkml.kernel.org/lkml/0000000000005e6124058c0cbdbe@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+88533dc8b582309bf3ee@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/0000000000005e6124058c0cbdbe@google.com
--------------------------------------------------------------------------------
Title: memory leak in rawv6_sendmsg
Last occurred: 30 days ago
Reported: 47 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=4b6cb10258f6d4c0f37be902f90849a02749a333
Original thread: https://lkml.kernel.org/lkml/000000000000fa6b60058aa0559b@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+0210b383c62bb2a35e32@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/000000000000fa6b60058aa0559b@google.com
--------------------------------------------------------------------------------
Title: general protection fault in drain_workqueue
Last occurred: 12 days ago
Reported: 71 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=4a4b04b94b33e7d1de6f1213355499ab529a3018
Original thread: https://lkml.kernel.org/lkml/000000000000caab290588c4083e@google.com/T/#u
This bug has a syzkaller reproducer only.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+09139d1a5ed6b898e29d@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/000000000000caab290588c4083e@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in ip_rcv_core
Last occurred: 36 days ago
Reported: 310 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=abe95dc3e3e9667fc23b8d81f29ecad95c6f106f
Original thread: https://lkml.kernel.org/lkml/0000000000002407700575fb00f4@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+2e406a9ac75bb71d4b7a@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/0000000000002407700575fb00f4@google.com
--------------------------------------------------------------------------------
Title: WARNING in wa_nep_create/usb_submit_urb
Last occurred: 13 days ago
Reported: 13 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=a07f49ea1871dcb4a34ff5aff5a46b0fcd8b3523
Original thread: https://lkml.kernel.org/lkml/000000000000acb38c058d51ad4f@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+5da93055dfbb6bc54963@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/000000000000acb38c058d51ad4f@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Write in skb_release_data (2)
Last occurred: 117 days ago
Reported: 281 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=8340d4b8c7304ff0b43490a1b69ab3833dd7ad20
Original thread: https://lkml.kernel.org/lkml/0000000000003ba80905783e9189@google.com/T/#u
This bug has a C reproducer.
This bug was bisected to:
commit 472c2e07eef045145bc1493cc94a01c87140780a
Author: Eric Dumazet <edumazet@google.com>
Date: Fri Mar 22 15:56:39 2019 +0000
tcp: add one skb cache for tx
The original thread for this bug received 3 replies; the last was 119 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+580be3953ed99133804f@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/0000000000003ba80905783e9189@google.com
--------------------------------------------------------------------------------
Title: general protection fault in ip6_dst_lookup_tail (2)
Last occurred: 34 days ago
Reported: 85 days ago
Branches: bpf-next, linux-next, net, and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=079bd8408abd95b492f127edf0df44ddc09d9405
Original thread: https://lkml.kernel.org/lkml/0000000000006b30f30587a5b569@google.com/T/#u
This bug has a syzkaller reproducer only.
This bug was bisected to:
commit f40b6ae2b612446dc970d7b51eeec47bd1619f82
Author: David Ahern <dsahern@gmail.com>
Date: Thu May 23 03:27:55 2019 +0000
ipv6: Move pcpu cached routes to fib6_nh
The original thread for this bug has received 1 reply, 85 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+58d8f704b86e4e3fb4d3@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/0000000000006b30f30587a5b569@google.com
--------------------------------------------------------------------------------
Title: general protection fault in cdev_del
Last occurred: 47 days ago
Reported: 56 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=dc0ead75c30e6aa27153b6cab86194e55e290a98
Original thread: https://lkml.kernel.org/lkml/000000000000532b860589f0669a@google.com/T/#u
This bug has a C reproducer.
No one has replied to the original thread for this bug yet.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+67b2bd0e34f952d0321e@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/000000000000532b860589f0669a@google.com
--------------------------------------------------------------------------------
Title: INFO: task hung in addrconf_dad_work
Last occurred: 23 days ago
Reported: 157 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=7293d6f37a448b017658dc1001452ff193cdb566
Original thread: https://lkml.kernel.org/lkml/0000000000001d37cd0582003c53@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+f4290c15a8ab6dee87c9@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/0000000000001d37cd0582003c53@google.com
--------------------------------------------------------------------------------
Title: WARNING: ODEBUG bug in netdev_freemem (2)
Last occurred: 0 days ago
Reported: 29 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=96a64fde216dca408a5c25db4e57838c51e435aa
Original thread: https://lkml.kernel.org/lkml/000000000000d6a8ba058c0df076@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug has received 6 replies; the last was 29 days
ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+c4521ac872a4ccc3afec@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/000000000000d6a8ba058c0df076@google.com
--------------------------------------------------------------------------------
Title: memory leak in genl_register_family
Last occurred: 28 days ago
Reported: 28 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=e30aad348314bcaacef4466bbce33be5933e08cf
Original thread: https://lkml.kernel.org/lkml/000000000000f5d536058c23ed60@google.com/T/#u
This bug has a syzkaller reproducer only.
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+fc577f12f25f2ac3b211@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/000000000000f5d536058c23ed60@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in __dev_mc_del
Last occurred: 86 days ago
Reported: 309 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=a84ac404cf07db753e289b918981964b540359bd
Original thread: https://lkml.kernel.org/lkml/00000000000011d524057617eb4a@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+0ffee94c5c059dbbc2a9@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/00000000000011d524057617eb4a@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in __dev_queue_xmit (2)
Last occurred: 1 day ago
Reported: 117 days ago
Branches: bpf-next and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=f9e1abb5bf1d75834c1906398efab4601265cad5
Original thread: https://lkml.kernel.org/lkml/000000000000ee01ef058529d74c@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+f8c40b4da41f3e8049c4@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/000000000000ee01ef058529d74c@google.com
--------------------------------------------------------------------------------
Title: WARNING: locking bug in udpv6_pre_connect
Last occurred: 2 days ago
Reported: 68 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=360cc28d22ff388dcda1dd642c5c77aa4b8b3e2d
Original thread: https://lkml.kernel.org/lkml/0000000000003028060588fac869@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+65f10c5aadc049eb5ef5@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/0000000000003028060588fac869@google.com
--------------------------------------------------------------------------------
Title: WARNING: locking bug in do_ipv6_getsockopt
Last occurred: 21 days ago
Reported: 21 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=e97be0bf4d30813e951bcc6249e72c592a790164
Original thread: https://lkml.kernel.org/lkml/000000000000607bf4058cb5135c@google.com/T/#u
This bug has a syzkaller reproducer only.
The original thread for this bug has received 1 reply, 21 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+babfdd7368c72aac3875@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/000000000000607bf4058cb5135c@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in IP6_ECN_decapsulate
Last occurred: 401 days ago
Reported: 306 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=ca4ff394c64aec3684d0034896290c72a83b7077
Original thread: https://lkml.kernel.org/lkml/000000000000336563057653b9aa@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+bf7e6250c7ce248f3ec9@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/000000000000336563057653b9aa@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in tick_sched_handle (3)
Last occurred: 190 days ago
Reported: 246 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=fce6ae4655ae3133b8b7410c3370bb2167c6324d
Original thread: https://lkml.kernel.org/lkml/0000000000007829c8057b0b58ed@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 2 replies; the last was 245 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+999bca54de2ee169c021@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/0000000000007829c8057b0b58ed@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in strlcpy (2)
Last occurred: 321 days ago
Reported: 312 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=ab0817a1599dd2fbbda6af5d5645ef92596fcb8e
Original thread: https://lkml.kernel.org/lkml/00000000000012463d0575d8eace@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+c86cf7903306a6c201ba@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/00000000000012463d0575d8eace@google.com
--------------------------------------------------------------------------------
Title: INFO: trying to register non-static key in __icmp_send
Last occurred: 42 days ago
Reported: 139 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=8375400c5f4e129bf049227adce14e4698a4bc33
Original thread: https://lkml.kernel.org/lkml/000000000000de803205836436dd@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+f09d845ad631ed93737b@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/000000000000de803205836436dd@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in vhci_hub_control
Last occurred: 278 days ago
Reported: 323 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=00aa2c9aba775f0761d3dabd7fb176964685051a
Original thread: https://lkml.kernel.org/lkml/00000000000075c8d70574f40fbc@google.com/T/#u
This bug has a C reproducer.
No one replied to the original thread for this bug.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+600b03e0cf1b73bb23c4@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/00000000000075c8d70574f40fbc@google.com
--------------------------------------------------------------------------------
Title: WARNING: refcount bug in igmp_start_timer
Last occurred: 100 days ago
Reported: 339 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=667f1bd0ab632a49ca3daaa6967cc023b1c5b0c6
Original thread: https://lkml.kernel.org/lkml/0000000000002b42040573b8495a@google.com/T/#u
This bug has a syzkaller reproducer only.
syzbot has bisected this bug, but I think the bisection result is incorrect.
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+e28037ac1c96d2a86e89@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/0000000000002b42040573b8495a@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in sit_tunnel_xmit
Last occurred: 230 days ago
Reported: 361 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=66bbedf52134d2359166806349088d36a6b6a254
Original thread: https://lkml.kernel.org/lkml/00000000000082e3a90571fadb4c@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+782ee96f9147673d8822@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/00000000000082e3a90571fadb4c@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in gre_rcv (2)
Last occurred: 140 days ago
Reported: 300 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=cf4a7c5922ce5ad229f97ed1eac213a12d427d1d
Original thread: https://lkml.kernel.org/lkml/0000000000007ce3ae0576c788e5@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+841c053d026900055032@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/0000000000007ce3ae0576c788e5@google.com
--------------------------------------------------------------------------------
Title: WARNING: locking bug in lock_sock_nested
Last occurred: 81 days ago
Reported: 100 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=a9f61ee7d10b848190610b0fe298bd9030a8288c
Original thread: https://lkml.kernel.org/lkml/000000000000e8cf3805867bd715@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+605a69fff339d9cc221e@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/000000000000e8cf3805867bd715@google.com
--------------------------------------------------------------------------------
Title: KMSAN: uninit-value in __dev_mc_add
Last occurred: 104 days ago
Reported: 300 days ago
Branches: Mainline (with KMSAN patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=0766d38c656abeace60621896d705743aeefed51
Original thread: https://lkml.kernel.org/lkml/0000000000005e2e530576c6f9ce@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 3 replies; the last was 299 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+001516d86dbe88862cec@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/0000000000005e2e530576c6f9ce@google.com
--------------------------------------------------------------------------------
Title: INFO: task hung in do_ip_vs_set_ctl (2)
Last occurred: 457 days ago
Reported: 472 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=26aa22915f5e3b7ca2cfca76a939f12c25d624db
Original thread: https://lkml.kernel.org/lkml/94eb2c059ce0bca273056940d77d@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+7810ed2e0cb359580c17@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/94eb2c059ce0bca273056940d77d@google.com
--------------------------------------------------------------------------------
Title: KASAN: null-ptr-deref Read in ip6_hold_safe
Last occurred: 35 days ago
Reported: 190 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=9b5576748203154c7b7703aac19d0a5adc8f987e
Original thread: https://lkml.kernel.org/lkml/00000000000075c0ef057f657b8d@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug received 1 reply, 190 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+8433ca0841e308ef4cc7@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/00000000000075c0ef057f657b8d@google.com
--------------------------------------------------------------------------------
Title: INFO: task hung in rtnetlink_rcv_msg
Last occurred: 156 days ago
Reported: 151 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=788ed2c7e973b69fd551ba6b5e21848dba2c1670
Original thread: https://lkml.kernel.org/lkml/000000000000c07a5805827e85d5@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 7 replies; the last was 148 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+8218a8a0ff60c19b8eae@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/000000000000c07a5805827e85d5@google.com
--------------------------------------------------------------------------------
Title: general protection fault in dev_get_by_index_rcu
Last occurred: 30 days ago
Reported: 152 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=e9d52597e9cbdd22621b6790702c9fefe071af25
Original thread: https://lkml.kernel.org/lkml/00000000000095c8f005826888fd@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+48127bec5a5cd81411e3@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/00000000000095c8f005826888fd@google.com
--------------------------------------------------------------------------------
Title: general protection fault in gro_cells_destroy
Last occurred: 30 days ago
Reported: 194 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=1e493023b2e9f4b6738977af63ed5b521201e74a
Original thread: https://lkml.kernel.org/lkml/00000000000029bf02057f1e1596@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+6fe674089f9deb9f7726@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/00000000000029bf02057f1e1596@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in device_del
Last occurred: 51 days ago
Reported: 50 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=2aa2f730c9d353ad29bb92acf8fd0b426ce1b393
Original thread: https://lkml.kernel.org/lkml/000000000000fa11f3058a69d67b@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug has received 2 replies; the last was 47 days
ago.
This looks like a bug in a net USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+93f2f45b19519b289613@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/000000000000fa11f3058a69d67b@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in tcp_sk_exit
Last occurred: 36 days ago
Reported: 167 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=24c7faa7497a843d2c714efffcc747853c55b669
Original thread: https://lkml.kernel.org/lkml/000000000000ddb37c0581329cc5@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+f797267da5e5012d0920@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/000000000000ddb37c0581329cc5@google.com
--------------------------------------------------------------------------------
Title: WARNING in tcp_enter_loss (2)
Last occurred: 448 days ago
Reported: 498 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=b0bacf5645b1e60bbb14015bc0e23b9019621fc4
Original thread: https://groups.google.com/d/msgid/syzkaller-bugs/001a113f39820d16d50567379661%40google.com
This bug has a C reproducer.
For some reason the original report email for this bug is missing from the LKML
archive at lore.kernel.org, so my script couldn't check whether anyone has
replied to it or not. The Google Groups link above should still work, though.
Also try searching for the bug title.
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in ip6_tnl_parse_tlv_enc_lim
Last occurred: 240 days ago
Reported: 309 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=b321cffb2022132bac9c54cbe0adcab20cfdd911
Original thread: https://lkml.kernel.org/lkml/0000000000005175bf057617c71d@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+68dce7caebd8543121de@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/0000000000005175bf057617c71d@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in ip_send_unicast_reply
Last occurred: 31 days ago
Reported: 167 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=b2fcf1ea1f7f874f9ae3ede65e0f47e82a02b3a1
Original thread: https://lkml.kernel.org/lkml/0000000000005e6094058132a09a@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+f1741fbf71635c029556@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/0000000000005e6094058132a09a@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in page_get_anon_vma
Last occurred: 26 days ago
Reported: 77 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=c275ff8b0b025c8a9baf06c3799d5c2efb919b56
Original thread: https://lkml.kernel.org/lkml/0000000000008aa0e4058849190e@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+ed3e5c9a6a1e30a1bd2a@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/0000000000008aa0e4058849190e@google.com
--------------------------------------------------------------------------------
Title: WARNING: ODEBUG bug in del_timer (3)
Last occurred: 64 days ago
Reported: 77 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=d1853700c9f62752d8498e05189f5d0f21a55631
Original thread: https://lkml.kernel.org/lkml/000000000000dace5e0588529558@google.com/T/#u
This bug has a syzkaller reproducer only.
The original thread for this bug has received 1 reply, 77 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+13d91ed9bbcd7dc13230@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/000000000000dace5e0588529558@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at net/ipv6/route.c:LINE! (2)
Last occurred: 31 days ago
Reported: 197 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=5789609f5b68813f3bf496c9786b9df683dbaa2f
Original thread: https://lkml.kernel.org/lkml/000000000000114562057edb528d@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+be0943c590bb47aefb9e@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/000000000000114562057edb528d@google.com
--------------------------------------------------------------------------------
Title: INFO: trying to register non-static key in icmp_send
Last occurred: 154 days ago
Reported: 175 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=ea46a31df5253b18deb1e18c429c1483b111cbce
Original thread: https://lkml.kernel.org/lkml/0000000000007cd20e05809c2f96@google.com/T/#u
This bug has a syzkaller reproducer only.
syzbot has bisected this bug, but I think the bisection result is incorrect.
The original thread for this bug received 1 reply, 121 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+e1628a5e87492e6f1b76@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/0000000000007cd20e05809c2f96@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in ip6_hold_safe
Last occurred: 37 days ago
Reported: 152 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=16a5da76273f5052f30015161c9bd05153bc1172
Original thread: https://lkml.kernel.org/lkml/0000000000003209980582688c5b@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+ec03ae3a032901d10434@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/0000000000003209980582688c5b@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in tcp_sk_exit
Last occurred: 53 days ago
Reported: 138 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=3901fe419ff5f17d6a1607b7d6d79c629a571946
Original thread: https://lkml.kernel.org/lkml/000000000000071b3c05838536b8@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+dfc9db054bca3a83f4a0@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/000000000000071b3c05838536b8@google.com
--------------------------------------------------------------------------------
Title: KASAN: user-memory-access Write in dst_release
Last occurred: 39 days ago
Reported: 197 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=c6269996e9feee38b279462027a03d4e49df1162
Original thread: https://lkml.kernel.org/lkml/000000000000a06f21057edc53c0@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+29ffc731816e0995ad54@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/000000000000a06f21057edc53c0@google.com
--------------------------------------------------------------------------------
Title: WARNING in csum_and_copy_to_iter
Last occurred: 243 days ago
Reported: 241 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=602b1f5d93c8e231d50a1424c2fbc3318bcc6833
Original thread: https://lkml.kernel.org/lkml/0000000000001ecaa1057b6e4489@google.com/T/#u
This bug has a syzkaller reproducer only.
The original thread for this bug received 5 replies; the last was 239 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+ce18da013d76d837144d@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/0000000000001ecaa1057b6e4489@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in sch_direct_xmit
Last occurred: 476 days ago
Reported: 553 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=3b9ee8a71fc404315ece5d56076775a2ed19ce1d
Original thread: https://lkml.kernel.org/lkml/089e0825d4a4d2cb2a0562e878f1@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+29cc278357da941e304e@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/089e0825d4a4d2cb2a0562e878f1@google.com
--------------------------------------------------------------------------------
Title: WARNING: bad unlock balance detected! (3)
Last occurred: 119 days ago
Reported: 149 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=342beb2b368a43cbb6533c00d758759b10fbc8d8
Original thread: https://lkml.kernel.org/lkml/000000000000685dc805829e835c@google.com/T/#u
This bug has a syzkaller reproducer only.
syzbot has bisected this bug, but I think the bisection result is incorrect.
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+f3e3434787332dfc1c47@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/000000000000685dc805829e835c@google.com
--------------------------------------------------------------------------------
Title: inconsistent lock state in ila_xlat_nl_cmd_del_mapping
Last occurred: 337 days ago
Reported: 343 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=be943a4399dcf3ed43bac2694a3b8957c6980409
Original thread: https://lkml.kernel.org/lkml/000000000000ae453e05735dcdb8@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+3db64bd48b29a825d2db@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/000000000000ae453e05735dcdb8@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at net/ipv4/ip_output.c:LINE!
Last occurred: 184 days ago
Reported: 375 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=d582be84c0efa34f4936e12227905b2c18989a25
Original thread: https://lkml.kernel.org/lkml/000000000000f68d660570dcddd8@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+90d5ec0c05e708f3b66d@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/000000000000f68d660570dcddd8@google.com
--------------------------------------------------------------------------------
Title: KASAN: null-ptr-deref Write in dst_release
Last occurred: 35 days ago
Reported: 197 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=e25580ce7d7f1e6c3bed77954ec56dfd7ce89805
Original thread: https://lkml.kernel.org/lkml/00000000000012073a057edb3996@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+1f4f4025b8564c8da9d4@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/00000000000012073a057edb3996@google.com
--------------------------------------------------------------------------------
Title: general protection fault in fib6_nh_init
Last occurred: 34 days ago
Reported: 49 days ago
Branches: bpf-next and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=29b9955ae85cdd2f20baf5d975763a446f2783df
Original thread: https://lkml.kernel.org/lkml/0000000000008ee293058a787e2d@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug has received 1 reply, 48 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+1b2927fda48c5bf2e931@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/0000000000008ee293058a787e2d@google.com
--------------------------------------------------------------------------------
Title: general protection fault in tcp_v6_connect
Last occurred: 35 days ago
Reported: 52 days ago
Branches: bpf-next and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=71eb43337087b631994f0811b2d84dfbc4bfcfc4
Original thread: https://lkml.kernel.org/lkml/000000000000aa7a27058a3ce9aa@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+5ee26b4e30c45930bd3c@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/000000000000aa7a27058a3ce9aa@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in icmp_sk_exit
Last occurred: 140 days ago
Reported: 153 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=0cbaf5f5094157a8d563c6c1cbe5ee20028a8902
Original thread: https://lkml.kernel.org/lkml/000000000000b436ad058255c528@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+3d7fa0f0de0f86d0eb4f@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/000000000000b436ad058255c528@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in bond_get_stats (2)
Last occurred: 64 days ago
Reported: 232 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=ea28d585e25ade2dde266036c70df752bb3a0fcb
Original thread: https://lkml.kernel.org/lkml/000000000000dd0b51057c263f7f@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+de40a1dd58ea38aa9317@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/000000000000dd0b51057c263f7f@google.com
--------------------------------------------------------------------------------
Title: inconsistent lock state in ila_xlat_nl_cmd_add_mapping
Last occurred: 337 days ago
Reported: 343 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=481b4913494f0dcabc2e06e3158a3d042abdf985
Original thread: https://lkml.kernel.org/lkml/000000000000b14d8c05735dcdf8@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+eaaf6c4a6a8cb1869d86@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/000000000000b14d8c05735dcdf8@google.com
--------------------------------------------------------------------------------
Title: general protection fault in __queue_work
Last occurred: 139 days ago
Reported: 138 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=1401c87c1eac8167422bcdb28cf81647d894e8d2
Original thread: https://lkml.kernel.org/lkml/000000000000aec29a0583853924@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+b26e643d0aa2822e9c87@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/000000000000aec29a0583853924@google.com
--------------------------------------------------------------------------------
Title: WARNING in remove_proc_entry (2)
Last occurred: 90 days ago
Reported: 244 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=fab7eb1ff4259eb5e6cb9067cba63ec7b1568b4d
Original thread: https://lkml.kernel.org/lkml/00000000000061c4cf057b306863@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+46d1fec9e51890edb1a6@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/00000000000061c4cf057b306863@google.com
--------------------------------------------------------------------------------
Title: general protection fault in __sock_release (2)
Last occurred: 36 days ago
Reported: 174 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=6997b9812b85ed88863bddecad772e8d3659e358
Original thread: https://lkml.kernel.org/lkml/000000000000559d460580ad5eeb@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+38b29941610a1cc735dc@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/000000000000559d460580ad5eeb@google.com
--------------------------------------------------------------------------------
Title: WARNING in __static_key_slow_dec_cpuslocked
Last occurred: 80 days ago
Reported: 77 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=753aa2e459553231bb71e1602b2cd27171a06d32
Original thread: https://lkml.kernel.org/lkml/000000000000759a89058848e747@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+a65e6ce239e4afe6c5e7@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/000000000000759a89058848e747@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in sk_diag_fill
Last occurred: 65 days ago
Reported: 444 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=3968882ac771e7458b15f8086477f42d7ca6dec0
Original thread: https://lkml.kernel.org/lkml/000000000000169606056b793179@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug received 6 replies; the last was 434 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+c1872be62e587eae9669@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/000000000000169606056b793179@google.com
--------------------------------------------------------------------------------
Title: general protection fault in fib6_purge_rt (2)
Last occurred: 43 days ago
Reported: 91 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=e017f309864dbdc2a6926d235e0ce85b6272dcfd
Original thread: https://lkml.kernel.org/lkml/000000000000caeb1c058734c654@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+d53d5d9b6793dc70eb9d@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/000000000000caeb1c058734c654@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in icmpv6_xrlim_allow
Last occurred: 38 days ago
Reported: 49 days ago
Branches: bpf-next
Dashboard link: https://syzkaller.appspot.com/bug?id=d22f32efcb9496c8fa450f963bcce4d3e4cdf09d
Original thread: https://lkml.kernel.org/lkml/000000000000ae08b2058a785a4c@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+14536436e78408172703@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/000000000000ae08b2058a785a4c@google.com
--------------------------------------------------------------------------------
Title: KASAN: user-memory-access Write in fib6_purge_rt (2)
Last occurred: 42 days ago
Reported: 49 days ago
Branches: net
Dashboard link: https://syzkaller.appspot.com/bug?id=29ea3db1b7655bdcf69bc0e3d8e5901623444640
Original thread: https://lkml.kernel.org/lkml/0000000000003f73d9058a785eec@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+420d3f70afb5d69d5a96@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/0000000000003f73d9058a785eec@google.com
--------------------------------------------------------------------------------
Title: BUG: spinlock bad magic in __queue_work
Last occurred: 119 days ago
Reported: 167 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=27ee7c254659d57dd99215715f3db0ed20339941
Original thread: https://lkml.kernel.org/lkml/000000000000e063bb0581329cc0@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+636bcaf4b481f6b7343c@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/000000000000e063bb0581329cc0@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in genl_rcv (2)
Last occurred: 133 days ago
Reported: 193 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=f8a6b7d881874def4c37657fac2453f7551a7664
Original thread: https://lkml.kernel.org/lkml/000000000000827dbb057f2b85bb@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+cf29f8ae16ca7ceb483d@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/000000000000827dbb057f2b85bb@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in fib6_purge_rt (2)
Last occurred: 50 days ago
Reported: 49 days ago
Branches: net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=4174cd9494cb4571668f34ab96fcb2382554e6fb
Original thread: https://lkml.kernel.org/lkml/000000000000b6a7d2058a78736d@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+f4812f31edd866494c9f@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/000000000000b6a7d2058a78736d@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in fib6_rule_lookup (2)
Last occurred: 52 days ago
Reported: 116 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=148148cb145574b07580d9e34877b4eef587ed31
Original thread: https://lkml.kernel.org/lkml/00000000000021ef3505853f988e@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+49f38f33f3c5d76cb19b@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/00000000000021ef3505853f988e@google.com
--------------------------------------------------------------------------------
Title: KASAN: wild-memory-access Write in fib6_purge_rt
Last occurred: 86 days ago
Reported: 165 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=e3ed1520f5d50c003569cc69066d780ef2ee9f18
Original thread: https://lkml.kernel.org/lkml/000000000000ca08dd0581649889@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+3dbea54db3674c0d57d6@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/000000000000ca08dd0581649889@google.com
--------------------------------------------------------------------------------
Title: WARNING: locking bug in try_to_grab_pending
Last occurred: 161 days ago
Reported: 160 days ago
Branches: net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=86c7f0dd3bfa4cd651bb37a04da2cfcabd860225
Original thread: https://lkml.kernel.org/lkml/0000000000006dc0290581ca413e@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+2b713236b28823cd4dff@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/0000000000006dc0290581ca413e@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in skb_queue_tail
Last occurred: 125 days ago
Reported: 477 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=ab5525a0b79efd6a5dbb4deb3ccd3e93d9c03321
Original thread: https://lkml.kernel.org/lkml/0000000000003584570568da18dd@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug received 5 replies; the last was 475 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+6b495100f17ca8554ab9@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/0000000000003584570568da18dd@google.com
--------------------------------------------------------------------------------
Title: WARNING: locking bug in icmp6_send (2)
Last occurred: 44 days ago
Reported: 42 days ago
Branches: net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=2ccdf5f785fdb1087d9dc106dd8bc71ea9a1fb58
Original thread: https://lkml.kernel.org/lkml/000000000000e64753058b06f83f@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+0ee50f3d30ce6a28b3cd@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/000000000000e64753058b06f83f@google.com
--------------------------------------------------------------------------------
Title: general protection fault in ipv6_rcv
Last occurred: 73 days ago
Reported: 136 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=6a14da2954543d26e61aeaefa0098d445854c5c1
Original thread: https://lkml.kernel.org/lkml/0000000000001b05b40583a46fd7@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+6c54e67cc0b0c896aa4b@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/0000000000001b05b40583a46fd7@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in neigh_change_state
Last occurred: 211 days ago
Reported: 223 days ago
Branches: bpf-next, linux-next, and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=9a91353fc2af7d4f3085766dadc9105304c7e7c4
Original thread: https://lkml.kernel.org/lkml/000000000000029056057cd141cb@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+6a3c02010a025ac7b7cf@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/000000000000029056057cd141cb@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in ip_tunnel_lookup
Last occurred: 114 days ago
Reported: 190 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=0a2ec3432ccfbd144e44c746f5b7b04f7e12c989
Original thread: https://lkml.kernel.org/lkml/00000000000075901d057f6e5a97@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+4a0034797afb7e908ab4@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/00000000000075901d057f6e5a97@google.com
--------------------------------------------------------------------------------
Title: general protection fault in ip6_dst_hoplimit
Last occurred: 131 days ago
Reported: 126 days ago
Branches: net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=e310a1a3031be03dae5de35cc6dd9782232fdfea
Original thread: https://lkml.kernel.org/lkml/000000000000df93f705846f0963@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
The original thread for this bug received 1 reply, 85 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+4c869fc20129562c53fa@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/000000000000df93f705846f0963@google.com
--------------------------------------------------------------------------------
Title: INFO: rcu detected stall in gc_worker
Last occurred: 97 days ago
Reported: 182 days ago
Branches: net and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=298ba9ab760957e0ead590f868a922d7d74bf59a
Original thread: https://lkml.kernel.org/lkml/000000000000ada99c058010d943@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+655174276c47216abab5@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/000000000000ada99c058010d943@google.com
--------------------------------------------------------------------------------
Title: WARNING in fib6_add (2)
Last occurred: 94 days ago
Reported: 235 days ago
Branches: bpf and net-next
Dashboard link: https://syzkaller.appspot.com/bug?id=757f2e8c1748d9d3b453b0ae3c33b1fbfe222d48
Original thread: https://lkml.kernel.org/lkml/0000000000000874de057be144e8@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+60cc5bc1296c8afcf739@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/0000000000000874de057be144e8@google.com
--------------------------------------------------------------------------------
Title: BUG: corrupted list in proto_register
Last occurred: 66 days ago
Reported: 66 days ago
Branches: net
Dashboard link: https://syzkaller.appspot.com/bug?id=a56a4bec03bf7561b1ec51fe929cba4018081b92
Original thread: https://lkml.kernel.org/lkml/000000000000e76a90058923eff3@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+7bc2817ec0ed18de9079@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/000000000000e76a90058923eff3@google.com
--------------------------------------------------------------------------------
Title: possible deadlock in dev_uc_sync_multiple
Last occurred: 130 days ago
Reported: 130 days ago
Branches: net
Dashboard link: https://syzkaller.appspot.com/bug?id=43071175d7c477c40dd1044a2ce30779a40ca4c0
Original thread: https://lkml.kernel.org/lkml/00000000000019ca8105842a9660@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+829513abde137358d25d@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/00000000000019ca8105842a9660@google.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 1:38 Reminder: 99 open syzbot bugs in net subsystem Eric Biggers
@ 2019-07-24 6:39 ` Eric Dumazet
2019-07-24 16:30 ` Eric Biggers
0 siblings, 1 reply; 14+ messages in thread
From: Eric Dumazet @ 2019-07-24 6:39 UTC (permalink / raw)
To: netdev, David S. Miller, Florian Westphal, Ilya Maximets,
Eric Dumazet, David Ahern, linux-kernel, syzkaller-bugs
On 7/24/19 3:38 AM, 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 99 of them as possibly being bugs in the net subsystem. This category
> only includes the networking bugs that I couldn't assign to a more specific
> component (bpf, xfrm, bluetooth, tls, tipc, sctp, wireless, etc.). 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 99 bugs, 17 were seen in mainline in the last week.
>
> Of these 99 bugs, 4 were bisected to commits from the following people:
>
> Florian Westphal <fw@strlen.de>
> Ilya Maximets <i.maximets@samsung.com>
> Eric Dumazet <edumazet@google.com>
> David Ahern <dsahern@gmail.com>
>
> 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 subsystem, please let me know,
> and if possible forward the report to the correct people or mailing list.
>
Some of the bugs have been fixed already, before syzbot found them.
Why force human to be gentle to bots and actually replying to them ?
I usually simply wait that syzbot is finding the bug does not repro anymore,
but now if you send these emails, we will have even more pressure on us.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 6:39 ` Eric Dumazet
@ 2019-07-24 16:30 ` Eric Biggers
2019-07-24 18:12 ` David Miller
0 siblings, 1 reply; 14+ messages in thread
From: Eric Biggers @ 2019-07-24 16:30 UTC (permalink / raw)
To: Eric Dumazet
Cc: Dmitry Vyukov, netdev, David S. Miller, Florian Westphal,
Ilya Maximets, Eric Dumazet, David Ahern, linux-kernel,
syzkaller-bugs
On Wed, Jul 24, 2019 at 08:39:05AM +0200, Eric Dumazet wrote:
>
>
> On 7/24/19 3:38 AM, 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 99 of them as possibly being bugs in the net subsystem. This category
> > only includes the networking bugs that I couldn't assign to a more specific
> > component (bpf, xfrm, bluetooth, tls, tipc, sctp, wireless, etc.). 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 99 bugs, 17 were seen in mainline in the last week.
> >
> > Of these 99 bugs, 4 were bisected to commits from the following people:
> >
> > Florian Westphal <fw@strlen.de>
> > Ilya Maximets <i.maximets@samsung.com>
> > Eric Dumazet <edumazet@google.com>
> > David Ahern <dsahern@gmail.com>
> >
> > 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 subsystem, please let me know,
> > and if possible forward the report to the correct people or mailing list.
> >
>
> Some of the bugs have been fixed already, before syzbot found them.
>
> Why force human to be gentle to bots and actually replying to them ?
>
> I usually simply wait that syzbot is finding the bug does not repro anymore,
> but now if you send these emails, we will have even more pressure on us.
>
First, based on experience, I'd guess about 30-45 of these are still valid. 17
were seen in mainline in the last week, but some others are valid too. The ones
most likely to still be valid are at the beginning of the list. So let's try
not use the presence of outdated bugs as an excuse not to fix current bugs.
Second, all these bug reports are still open, regardless of whether reminders
are sent or not. I think you're really suggesting that possibly outdated bug
reports should be automatically invalidated by syzbot.
syzbot already does that for bugs with no reproducer. However, that still
leaves a lot of outdated bugs with reproducers.
Since the kernel community is basically in continuous bug bankruptcy and lots of
syzbot reports are being ignored anyway, I'm in favor of making the invalidation
criteria more aggressive, so we can best focus people's efforts. I understand
that Dmitry has been against this though, since a significant fraction of bugs
that syzbot stopped hitting for some reason actually turn out to be still valid.
But we probably have no choice. So I suggest we agree on new criteria for
invalidating bugs. I'd suggest assigning a timeout to each bug, based on
attributes like "seen in mainline?", "reproducer type", "bisected?", "does it
look like a 'bad' crash (e.g. use-after-free)"; similar to the algorithm I'm
using to sort the bugs when sorting these reminders. I.e., bugs most likely to
still be valid, important, and actionable get longest timeouts.
Then if no crash or activity was seen in the timeout, the bug is closed.
Any thoughts from anyone?
- Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 16:30 ` Eric Biggers
@ 2019-07-24 18:12 ` David Miller
2019-07-24 18:37 ` Eric Biggers
0 siblings, 1 reply; 14+ messages in thread
From: David Miller @ 2019-07-24 18:12 UTC (permalink / raw)
To: ebiggers
Cc: eric.dumazet, dvyukov, netdev, fw, i.maximets, edumazet, dsahern,
linux-kernel, syzkaller-bugs
From: Eric Biggers <ebiggers@kernel.org>
Date: Wed, 24 Jul 2019 09:30:14 -0700
> On Wed, Jul 24, 2019 at 08:39:05AM +0200, Eric Dumazet wrote:
>> Some of the bugs have been fixed already, before syzbot found them.
>>
>> Why force human to be gentle to bots and actually replying to them ?
>>
>> I usually simply wait that syzbot is finding the bug does not repro anymore,
>> but now if you send these emails, we will have even more pressure on us.
>>
>
> First, based on experience, I'd guess about 30-45 of these are still valid. 17
> were seen in mainline in the last week, but some others are valid too. The ones
> most likely to still be valid are at the beginning of the list. So let's try
> not use the presence of outdated bugs as an excuse not to fix current bugs.
So about half of the bugs we are to look at are already fixed and thus
noise, even as estimated by you.
I agree with Eric, these "reminders" are bad for the people you
actually want to work on fixing these bugs.
> Since the kernel community is basically in continuous bug bankruptcy and lots of
I don't like this hyperbole. Please present facts and information we
can actually use to improve the kernel development and bug fixing
process.
Thank you.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 18:12 ` David Miller
@ 2019-07-24 18:37 ` Eric Biggers
2019-07-24 18:52 ` Eric Dumazet
2019-07-24 20:09 ` David Miller
0 siblings, 2 replies; 14+ messages in thread
From: Eric Biggers @ 2019-07-24 18:37 UTC (permalink / raw)
To: David Miller
Cc: eric.dumazet, dvyukov, netdev, fw, i.maximets, edumazet, dsahern,
linux-kernel, syzkaller-bugs
On Wed, Jul 24, 2019 at 11:12:25AM -0700, David Miller wrote:
> From: Eric Biggers <ebiggers@kernel.org>
> Date: Wed, 24 Jul 2019 09:30:14 -0700
>
> > On Wed, Jul 24, 2019 at 08:39:05AM +0200, Eric Dumazet wrote:
> >> Some of the bugs have been fixed already, before syzbot found them.
> >>
> >> Why force human to be gentle to bots and actually replying to them ?
> >>
> >> I usually simply wait that syzbot is finding the bug does not repro anymore,
> >> but now if you send these emails, we will have even more pressure on us.
> >>
> >
> > First, based on experience, I'd guess about 30-45 of these are still valid. 17
> > were seen in mainline in the last week, but some others are valid too. The ones
> > most likely to still be valid are at the beginning of the list. So let's try
> > not use the presence of outdated bugs as an excuse not to fix current bugs.
>
> So about half of the bugs we are to look at are already fixed and thus
> noise, even as estimated by you.
>
> I agree with Eric, these "reminders" are bad for the people you
> actually want to work on fixing these bugs.
Well, the problem is that no one knows for sure which bugs are fixed and which
aren't. To be certain, a human needs to review each bug. A bot can only guess.
Note that the bugs in my reminders are already automatically prioritized by how
likely they are to still be valid, important, actionable. So one simply needs
to start at the beginning of the list if they want to focus on those types of
bugs. Isn't this helpful?
>
> > Since the kernel community is basically in continuous bug bankruptcy and lots of
>
> I don't like this hyperbole. Please present facts and information we
> can actually use to improve the kernel development and bug fixing
> process.
>
A huge number of valid open bugs are not being fixed, which is a fact. We can
argue about what words to use to describe this situation, but it doesn't change
the situation itself.
What is your proposed solution?
- Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 18:37 ` Eric Biggers
@ 2019-07-24 18:52 ` Eric Dumazet
2019-07-24 19:03 ` Eric Biggers
2019-07-24 20:09 ` David Miller
1 sibling, 1 reply; 14+ messages in thread
From: Eric Dumazet @ 2019-07-24 18:52 UTC (permalink / raw)
To: David Miller, Eric Dumazet, Dmitry Vyukov, netdev,
Florian Westphal, i.maximets, Eric Dumazet, David Ahern, LKML,
syzkaller-bugs
On Wed, Jul 24, 2019 at 8:37 PM Eric Biggers <ebiggers@kernel.org> wrote:
> A huge number of valid open bugs are not being fixed, which is a fact. We can
> argue about what words to use to describe this situation, but it doesn't change
> the situation itself.
>
> What is your proposed solution?
syzbot sends emails, plenty of them, with many wrong bisection
results, increasing the noise.
If nobody is interested, I am not sure sending copies of them
repeatedly will be of any help.
Maybe a simple monthly reminder with one URL to go to the list of bugs
would be less intrusive.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 18:52 ` Eric Dumazet
@ 2019-07-24 19:03 ` Eric Biggers
0 siblings, 0 replies; 14+ messages in thread
From: Eric Biggers @ 2019-07-24 19:03 UTC (permalink / raw)
To: Eric Dumazet
Cc: David Miller, Eric Dumazet, Dmitry Vyukov, netdev,
Florian Westphal, i.maximets, David Ahern, LKML, syzkaller-bugs
On Wed, Jul 24, 2019 at 08:52:54PM +0200, 'Eric Dumazet' via syzkaller-bugs wrote:
> On Wed, Jul 24, 2019 at 8:37 PM Eric Biggers <ebiggers@kernel.org> wrote:
>
> > A huge number of valid open bugs are not being fixed, which is a fact. We can
> > argue about what words to use to describe this situation, but it doesn't change
> > the situation itself.
> >
> > What is your proposed solution?
>
> syzbot sends emails, plenty of them, with many wrong bisection
> results, increasing the noise.
>
> If nobody is interested, I am not sure sending copies of them
> repeatedly will be of any help.
>
> Maybe a simple monthly reminder with one URL to go to the list of bugs
> would be less intrusive.
>
The bogus bisection results is a known issue (which I'm trying to convince
Dmitry is important enough to fix...), which is why I manually reviewed all of
them and discarded out all the obviously incorrect ones. My reminders only
include manually reviewed bisection results. Obviously there will still be some
looked plausible but are actualy wrong, but I suspect the accuracy is around
80-90% rather than the 40-50% of the raw syzbot bisection results.
- Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 18:37 ` Eric Biggers
2019-07-24 18:52 ` Eric Dumazet
@ 2019-07-24 20:09 ` David Miller
2019-07-24 21:09 ` Eric Biggers
2019-07-25 3:39 ` Theodore Y. Ts'o
1 sibling, 2 replies; 14+ messages in thread
From: David Miller @ 2019-07-24 20:09 UTC (permalink / raw)
To: ebiggers
Cc: eric.dumazet, dvyukov, netdev, fw, i.maximets, edumazet, dsahern,
linux-kernel, syzkaller-bugs
From: Eric Biggers <ebiggers@kernel.org>
Date: Wed, 24 Jul 2019 11:37:12 -0700
> We can argue about what words to use to describe this situation, but
> it doesn't change the situation itself.
And we should argue about those words because it matters to humans and
effects how they feel, and humans ultimately fix these bugs.
So please stop with the hyperbole.
Thank you.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 20:09 ` David Miller
@ 2019-07-24 21:09 ` Eric Biggers
2019-07-25 5:04 ` Eric Dumazet
2019-07-25 3:39 ` Theodore Y. Ts'o
1 sibling, 1 reply; 14+ messages in thread
From: Eric Biggers @ 2019-07-24 21:09 UTC (permalink / raw)
To: David Miller
Cc: eric.dumazet, dvyukov, netdev, fw, i.maximets, edumazet, dsahern,
linux-kernel, syzkaller-bugs
On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
> From: Eric Biggers <ebiggers@kernel.org>
> Date: Wed, 24 Jul 2019 11:37:12 -0700
>
> > We can argue about what words to use to describe this situation, but
> > it doesn't change the situation itself.
>
> And we should argue about those words because it matters to humans and
> effects how they feel, and humans ultimately fix these bugs.
>
> So please stop with the hyperbole.
>
> Thank you.
Okay, there are 151 bugs that syzbot saw on the mainline Linux kernel in the
last 7 days (90.1% with reproducers). Of those, 59 were reported over 3 months
ago (89.8% with reproducers). Of those, 12 were reported over a year ago (83.3%
with reproducers).
No opinion on whether those are small/medium/large numbers, in case it would
hurt someone's feelings.
These numbers do *not* include bugs that are still valid but weren't seen on
mainline in last 7 days, e.g.:
- Bugs that are seen only rarely, so by chance weren't seen in last 7 days.
- Bugs only in linux-next and/or subsystem branches.
- Bugs that were seen in mainline more than 7 days ago, and then only on
linux-next or subsystem branch in last 7 days.
- Bugs that stopped being seen due to a change in syzkaller.
- Bugs that stopped being seen due to a change in kernel config.
- Bugs that stopped being seen due to other environment changes such as kernel
command line parameters.
- Bugs that stopped being seen due to a kernel change that hid the bug but
didn't actually fix it, i.e. still reachable in other ways.
Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 20:09 ` David Miller
2019-07-24 21:09 ` Eric Biggers
@ 2019-07-25 3:39 ` Theodore Y. Ts'o
2019-07-25 4:40 ` Eric Biggers
1 sibling, 1 reply; 14+ messages in thread
From: Theodore Y. Ts'o @ 2019-07-25 3:39 UTC (permalink / raw)
To: David Miller
Cc: ebiggers, eric.dumazet, dvyukov, netdev, fw, i.maximets,
edumazet, dsahern, linux-kernel, syzkaller-bugs
On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
> From: Eric Biggers <ebiggers@kernel.org>
> Date: Wed, 24 Jul 2019 11:37:12 -0700
>
> > We can argue about what words to use to describe this situation, but
> > it doesn't change the situation itself.
>
> And we should argue about those words because it matters to humans and
> effects how they feel, and humans ultimately fix these bugs.
>
> So please stop with the hyperbole.
Perhaps it would be better to call them, "syzbot reports". Not all
syzbot reports are bugs. In fact, Dmitry has steadfastly refused to
add features which any basic bug-tracking system would have, claiming
that syzbot should not be a bug-tracking system, and something like
bugzilla should be forcibly imposed on all kernel developers. So I
don't consider syzkaller reports as bugs --- they are just reports.
In order for developers to want to engage with "syzbot reports", we
need to reduce developer toil which syzbot imposes on developers, such
that it is a net benefit, instead of it being just a source of
annoying e-mails, some of which are actionable, and some of which are
noise.
In particular, asking developers to figure out which syzbot reports
should be closed, because developers found the problem independently,
and fixed it without hearing about from syzbot first, really isn't a
fair thing to ask. Especially if we can automate away the problem.
If there is a reproducer, it should be possible to automatically
categorize the reproducer as a reliable reproducer or a flakey one.
If it is a reliable reproducer on version X, and it fails to be
reliably reproduce on version X+N, then it should be able to figure
out that it has been fixed, instead of requesting that a human confirm
it. If you really want a human to look at it, now that syzkaller has
a bisection feature, it should be possible to use the reliable
reproducer to do a negative bisection search to report a candidate
fix. This would significantly reproduce the developer toil imposed as
a tax on developers. And if Dmitry doesn't want to auto-close those
reports that appear to be fixed already, at the very least they should
be down-prioritized on Eric's reports, so people who don't want to
waste their time on "bureaucracy" can do so.
Cheers,
- Ted
P.S. Another criteria I'd suggest down-prioritizing on is, "does it
require root privileges?" After all, since root has so many different
ways of crashing a system already, and if we're all super-busy, we
need to prioritize which reports should be addressed first.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-25 3:39 ` Theodore Y. Ts'o
@ 2019-07-25 4:40 ` Eric Biggers
0 siblings, 0 replies; 14+ messages in thread
From: Eric Biggers @ 2019-07-25 4:40 UTC (permalink / raw)
To: Theodore Y. Ts'o, David Miller, eric.dumazet, dvyukov,
netdev, fw, i.maximets, edumazet, dsahern, linux-kernel,
syzkaller-bugs
On Wed, Jul 24, 2019 at 11:39:13PM -0400, Theodore Y. Ts'o wrote:
> On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
> > From: Eric Biggers <ebiggers@kernel.org>
> > Date: Wed, 24 Jul 2019 11:37:12 -0700
> >
> > > We can argue about what words to use to describe this situation, but
> > > it doesn't change the situation itself.
> >
> > And we should argue about those words because it matters to humans and
> > effects how they feel, and humans ultimately fix these bugs.
> >
> > So please stop with the hyperbole.
>
> Perhaps it would be better to call them, "syzbot reports". Not all
> syzbot reports are bugs. In fact, Dmitry has steadfastly refused to
> add features which any basic bug-tracking system would have, claiming
> that syzbot should not be a bug-tracking system, and something like
> bugzilla should be forcibly imposed on all kernel developers. So I
> don't consider syzkaller reports as bugs --- they are just reports.
>
> In order for developers to want to engage with "syzbot reports", we
> need to reduce developer toil which syzbot imposes on developers, such
> that it is a net benefit, instead of it being just a source of
> annoying e-mails, some of which are actionable, and some of which are
> noise.
>
> In particular, asking developers to figure out which syzbot reports
> should be closed, because developers found the problem independently,
> and fixed it without hearing about from syzbot first, really isn't a
> fair thing to ask. Especially if we can automate away the problem.
>
> If there is a reproducer, it should be possible to automatically
> categorize the reproducer as a reliable reproducer or a flakey one.
> If it is a reliable reproducer on version X, and it fails to be
> reliably reproduce on version X+N, then it should be able to figure
> out that it has been fixed, instead of requesting that a human confirm
> it. If you really want a human to look at it, now that syzkaller has
> a bisection feature, it should be possible to use the reliable
> reproducer to do a negative bisection search to report a candidate
> fix. This would significantly reproduce the developer toil imposed as
> a tax on developers. And if Dmitry doesn't want to auto-close those
> reports that appear to be fixed already, at the very least they should
> be down-prioritized on Eric's reports, so people who don't want to
> waste their time on "bureaucracy" can do so.
>
> Cheers,
>
> - Ted
>
> P.S. Another criteria I'd suggest down-prioritizing on is, "does it
> require root privileges?" After all, since root has so many different
> ways of crashing a system already, and if we're all super-busy, we
> need to prioritize which reports should be addressed first.
>
I agree with all this. Fix bisection would be really useful. I think what we'd
actually need to do to get decent results, though, is consider many different
signals (days since last occurred, repro type, fix bisected, bug bisected,
occurred in mainline or not, does the repro work as root, is it clearly a "bad"
bug like use-after-free, etc.) and compute an appropriate timeout based on that.
However, I'd like to emphasize that in my reminder emails, I've *already*
considered many of these factors when sorting the bug reports, and in particular
the bugs/reports that have been seen recently are strongly weighted towards
being listed first, especially if they were seen in mainline. In this
particular reminder email, for example, the first 18 bugs/reports have *all*
been seen in the last 4 days.
These first 18 bugs/reports are ready to be worked on and fixed now. It's
unclear to me what is most impeding this. Is it part of the syzbot process?
Bad reproducers? Too much noise? Or is it no funding? Not enough qualified
people? No maintainers? Not enough reminders? Lack of CVEs and demonstrable
exploits? What is most impeding these 18 bugs from being fixed?
- Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-24 21:09 ` Eric Biggers
@ 2019-07-25 5:04 ` Eric Dumazet
2019-07-31 2:57 ` Eric Biggers
0 siblings, 1 reply; 14+ messages in thread
From: Eric Dumazet @ 2019-07-25 5:04 UTC (permalink / raw)
To: David Miller, eric.dumazet, dvyukov, netdev, fw, i.maximets,
edumazet, dsahern, linux-kernel, syzkaller-bugs
On 7/24/19 11:09 PM, Eric Biggers wrote:
> On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
>> From: Eric Biggers <ebiggers@kernel.org>
>> Date: Wed, 24 Jul 2019 11:37:12 -0700
>>
>>> We can argue about what words to use to describe this situation, but
>>> it doesn't change the situation itself.
>>
>> And we should argue about those words because it matters to humans and
>> effects how they feel, and humans ultimately fix these bugs.
>>
>> So please stop with the hyperbole.
>>
>> Thank you.
>
> Okay, there are 151 bugs that syzbot saw on the mainline Linux kernel in the
> last 7 days (90.1% with reproducers). Of those, 59 were reported over 3 months
> ago (89.8% with reproducers). Of those, 12 were reported over a year ago (83.3%
> with reproducers).
>
> No opinion on whether those are small/medium/large numbers, in case it would
> hurt someone's feelings.
>
> These numbers do *not* include bugs that are still valid but weren't seen on
> mainline in last 7 days, e.g.:
>
> - Bugs that are seen only rarely, so by chance weren't seen in last 7 days.
> - Bugs only in linux-next and/or subsystem branches.
> - Bugs that were seen in mainline more than 7 days ago, and then only on
> linux-next or subsystem branch in last 7 days.
> - Bugs that stopped being seen due to a change in syzkaller.
> - Bugs that stopped being seen due to a change in kernel config.
> - Bugs that stopped being seen due to other environment changes such as kernel
> command line parameters.
> - Bugs that stopped being seen due to a kernel change that hid the bug but
> didn't actually fix it, i.e. still reachable in other ways.
>
We do not doubt syzkaller is an incredible tool.
But netdev@ and lkml@ are mailing lists for humans to interact,
exchange ideas, send patches and review them.
To me, an issue that was reported to netdev by a real user is _way_ more important
than potential issues that a bot might have found doing crazy things.
We need to keep optimal S/N on mailing lists, so any bots trying to interact
with these lists must be very cautious and damn smart.
When I have time to spare and can work on syzbot reports, I am going to a web
page where I can see them and select the ones it makes sense to fix.
I hate having to set up email filters.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-25 5:04 ` Eric Dumazet
@ 2019-07-31 2:57 ` Eric Biggers
2019-07-31 15:13 ` David Ahern
0 siblings, 1 reply; 14+ messages in thread
From: Eric Biggers @ 2019-07-31 2:57 UTC (permalink / raw)
To: Eric Dumazet
Cc: David Miller, dvyukov, netdev, fw, i.maximets, edumazet, dsahern,
linux-kernel, syzkaller-bugs
On Thu, Jul 25, 2019 at 07:04:47AM +0200, Eric Dumazet wrote:
>
>
> On 7/24/19 11:09 PM, Eric Biggers wrote:
> > On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
> >> From: Eric Biggers <ebiggers@kernel.org>
> >> Date: Wed, 24 Jul 2019 11:37:12 -0700
> >>
> >>> We can argue about what words to use to describe this situation, but
> >>> it doesn't change the situation itself.
> >>
> >> And we should argue about those words because it matters to humans and
> >> effects how they feel, and humans ultimately fix these bugs.
> >>
> >> So please stop with the hyperbole.
> >>
> >> Thank you.
> >
> > Okay, there are 151 bugs that syzbot saw on the mainline Linux kernel in the
> > last 7 days (90.1% with reproducers). Of those, 59 were reported over 3 months
> > ago (89.8% with reproducers). Of those, 12 were reported over a year ago (83.3%
> > with reproducers).
> >
> > No opinion on whether those are small/medium/large numbers, in case it would
> > hurt someone's feelings.
> >
> > These numbers do *not* include bugs that are still valid but weren't seen on
> > mainline in last 7 days, e.g.:
> >
> > - Bugs that are seen only rarely, so by chance weren't seen in last 7 days.
> > - Bugs only in linux-next and/or subsystem branches.
> > - Bugs that were seen in mainline more than 7 days ago, and then only on
> > linux-next or subsystem branch in last 7 days.
> > - Bugs that stopped being seen due to a change in syzkaller.
> > - Bugs that stopped being seen due to a change in kernel config.
> > - Bugs that stopped being seen due to other environment changes such as kernel
> > command line parameters.
> > - Bugs that stopped being seen due to a kernel change that hid the bug but
> > didn't actually fix it, i.e. still reachable in other ways.
> >
>
> We do not doubt syzkaller is an incredible tool.
>
> But netdev@ and lkml@ are mailing lists for humans to interact,
> exchange ideas, send patches and review them.
>
> To me, an issue that was reported to netdev by a real user is _way_ more important
> than potential issues that a bot might have found doing crazy things.
>
> We need to keep optimal S/N on mailing lists, so any bots trying to interact
> with these lists must be very cautious and damn smart.
>
> When I have time to spare and can work on syzbot reports, I am going to a web
> page where I can see them and select the ones it makes sense to fix.
> I hate having to set up email filters.
>
syzbot finds a lot of security bugs, and security bugs are important. And the
bugs are still there regardless of whether they're reported by human or bot.
Also, there *are* bugs being fixed because of these reminders; some subsystem
maintainers have even fixed all the bugs in their subsystem. But I can
understand that for subsystems with a lot of open bug reports it's overwhelming.
What I'll try doing next time (if there *is* a next time; it isn't actually my
job to do any of this, I just care about the security and reliability of
Linux...) is for subsystems with lots of open bug reports, only listing the ones
actually seen in the last week or so, and perhaps also spending some more time
manually checking those bugs. That should cut down the noise a lot.
- Eric
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Reminder: 99 open syzbot bugs in net subsystem
2019-07-31 2:57 ` Eric Biggers
@ 2019-07-31 15:13 ` David Ahern
0 siblings, 0 replies; 14+ messages in thread
From: David Ahern @ 2019-07-31 15:13 UTC (permalink / raw)
To: Eric Dumazet, David Miller, dvyukov, netdev, fw, i.maximets,
edumazet, linux-kernel, syzkaller-bugs
On 7/30/19 8:57 PM, Eric Biggers wrote:
> syzbot finds a lot of security bugs, and security bugs are important. And the
> bugs are still there regardless of whether they're reported by human or bot.
>
> Also, there *are* bugs being fixed because of these reminders; some subsystem
> maintainers have even fixed all the bugs in their subsystem. But I can
> understand that for subsystems with a lot of open bug reports it's overwhelming.
>
> What I'll try doing next time (if there *is* a next time; it isn't actually my
> job to do any of this, I just care about the security and reliability of
> Linux...) is for subsystems with lots of open bug reports, only listing the ones
> actually seen in the last week or so, and perhaps also spending some more time
> manually checking those bugs. That should cut down the noise a lot.
I don't think anyone questions the overall value of syzbot. It's the
maintenance of bug reports that needs refining.
As an example, this one:
https://syzkaller.appspot.com/bug?id=079bd8408abd95b492f127edf0df44ddc09d9405
was in reality a very short-lived bug in net-next but because bpf-next
managed to merge net-next in the small time window, the bug life seems
more extended that it apparently was (fuzzy words since we do not know
which commit fixed it).
Also, there is inconsistency with the report. It shows a bisected commit of:
commit f40b6ae2b612446dc970d7b51eeec47bd1619f82
Author: David Ahern <dsahern@gmail.com>
Date: Thu May 23 03:27:55 2019 +0000
ipv6: Move pcpu cached routes to fib6_nh
yet the report shows an entry in net tree on April 27. Even the net
instance on June 14 is questionable given that the above commit is only
in net-next on June 14.
Taking all of those references out and there are 2 'real', unique
reports - the linux-next on May 31 and the net-next on June 5.
Given that nothing has appeared in the last 8 weeks it seems clear to me
that this bug has been fixed we just don't know by which commit.
If there is a way to reduce to some of that information or even to have
a button on that console that says 'apparently fixed' and close it would
be a help.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2019-07-31 15:18 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-24 1:38 Reminder: 99 open syzbot bugs in net subsystem Eric Biggers
2019-07-24 6:39 ` Eric Dumazet
2019-07-24 16:30 ` Eric Biggers
2019-07-24 18:12 ` David Miller
2019-07-24 18:37 ` Eric Biggers
2019-07-24 18:52 ` Eric Dumazet
2019-07-24 19:03 ` Eric Biggers
2019-07-24 20:09 ` David Miller
2019-07-24 21:09 ` Eric Biggers
2019-07-25 5:04 ` Eric Dumazet
2019-07-31 2:57 ` Eric Biggers
2019-07-31 15:13 ` David Ahern
2019-07-25 3:39 ` Theodore Y. Ts'o
2019-07-25 4:40 ` Eric Biggers
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).