Reminder: 1 open syzbot bug in rtc subsystem
[This email was generated by a script. Let me know if you have any suggestions to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually marked 1 of them as possibly being a bug in the rtc subsystem.
If you believe this 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 this bug to the rtc subsystem, please let me know, and if possible forward the report to the correct people or mailing list.
Here is the bug:
--------------------------------------------------------------------------------
Title: BUG: workqueue lockup (4) Last occurred: 40 days ago Reported: 289 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=0041bf1423916e9ae458b08b760e269a33c14960 Original thread: https://lkml.kernel.org/lkml/[email protected]/T/#u
This bug has a C reproducer.
The original thread for this bug received 4 replies; the last was 42 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: [email protected]
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/[email protected]
Quoted 6 lines · Eric Biggers
[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 1 of them as possibly being a bug in the rtc subsystem.
Quoted 8 lines
If you believe this 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 this bug to the rtc subsystem, please let me know, and if possible forward the report to the correct people or mailing list.
Here is the bug:
Can you stop spamming lkml?
Sending 20 "reminders" in a row is not something human would do, and it is not something your bot should be allowed to do, either.
Pavel
Quoted 14 lines · Pavel Machek
Quoted 13 lines · Eric Biggers
[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 1 of them as possibly being a bug in the rtc subsystem.
If you believe this 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 this bug to the rtc subsystem, please let me know, and if possible forward the report to the correct people or mailing list.
Quoted 8 lines
Quoted 1 line
Here is the bug:
Can you stop spamming lkml?
Sending 20 "reminders" in a row is not something human would do, and it is not something your bot should be allowed to do, either.
Hi Pavel, just to clarify, though I used a script to generate these emails, I manually reviewed and sent each one; I also manually assigned the subsystems and sanity checked the bisection results. (I'm also not on the syzbot team. I just care about the security and reliability of the Linux kernel...) The reason there are so many of these emails is that there are a lot of kernel subsystems with open bug reports, many clearly still valid -- even considering that I decided to skip some subsystems after deciding to just fix the bugs myself, update the bug statuses myself, send some other email, or just wait.
I suppose there's some argument to be made that it's too noisy to Cc linux-kernel when I've already assigned a subsystem, though, so I'll try dropping linux-kernel from Cc for next time and just using the subsystem list and maintainers, and see if that goes any better or worse.
Note that the syzbot reports themselves are still going to linux-kernel, though.
Thanks!
- Eric
Quoted 26 lines · Hillf Danton
On Tue, 23 Jul 2019 19:50:08 -0700
Quoted 16 lines
[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 1 of them as possibly being a bug in the rtc subsystem.
If you believe this 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 this bug to the rtc subsystem, please let me know, and if possible forward the report to the correct people or mailing list.
Here is the bug:
Quoted 8 lines
--------------------------------------------------------------------------------
Title: BUG: workqueue lockup (4) Last occurred: 40 days ago Reported: 289 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=0041bf1423916e9ae458b08b760e269a33c14960 Original thread: https://lkml.kernel.org/lkml/[email protected]/T/#u
Quoted 2 lines
Better if %s=lkml.kernel.org=lore.kernel.org=
Out of curiosity, is there a reason for this? They both go to the same place, but the reason I used lkml.kernel.org is that some high-profile kernel developers (e.g. Andrew Morton) are using it in the "Link: " tag in commits. So it seems like lkml.kernel.org is maybe "right" one that is intended to always keep working in the future?
But then I see Greg KH is using lore.kernel.org, so maybe it doesn't matter?
Maybe lore.kernel.org is better because people won't confuse it with lkml.org and refuse to go to it :-)
- Eric
Quoted 33 lines · Eric Biggers
Quoted 14 lines · Pavel Machek
Quoted 13 lines · Eric Biggers
[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 1 of them as possibly being a bug in the rtc subsystem.
If you believe this 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 this bug to the rtc subsystem, please let me know, and if possible forward the report to the correct people or mailing list.
Quoted 8 lines
Quoted 1 line
Here is the bug:
Can you stop spamming lkml?
Sending 20 "reminders" in a row is not something human would do, and it is not something your bot should be allowed to do, either.
Hi Pavel, just to clarify, though I used a script to generate these emails, I manually reviewed and sent each one; I also manually assigned the subsystems and sanity checked the bisection results. (I'm also not on the syzbot team. I just care about the security and reliability of the Linux kernel...) The reason there are so many of these emails is that there are a lot of kernel subsystems with open bug reports, many clearly still valid -- even considering that I decided to skip some subsystems after deciding to just fix the bugs myself, update the bug statuses myself, send some other email, or just wait.
Quoted 4 lines
I suppose there's some argument to be made that it's too noisy to Cc linux-kernel when I've already assigned a subsystem, though, so I'll try dropping linux-kernel from Cc for next time and just using the subsystem list and maintainers, and see if that goes any better or worse.
That should do the trick. Thanks!
Quoted 1 line
Note that the syzbot reports themselves are still going to linux-kernel, though.
Yes, I know. I'm not entirely sure that is good idea.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html