|
|
Log in / Subscribe / Register

Troubles with triaging syzbot reports

Troubles with triaging syzbot reports

Posted Dec 16, 2022 2:34 UTC (Fri) by NYKevin (subscriber, #129325)
In reply to: Troubles with triaging syzbot reports by rgmoore
Parent article: Troubles with triaging syzbot reports

As a Googler, I have to put up with this sort of thing (i.e. "here is an email/stderr message/log entry/whatnot, it contains a link, the link points to the actual information") so often that I'm basically immune to caring at this point. It's simply The Way Things Are Done over there.

(This is not meant to excuse it, merely to commiserate with other people being subjected to it.)

to post comments

Troubles with triaging syzbot reports

Posted Dec 16, 2022 17:44 UTC (Fri) by rgmoore (✭ supporter ✭, #75) [Link]

An email that points you to the information might be OK if you can at least have some confidence it's about your project. It's far worse when it's an email to a whole mailing list, most of whom aren't involved. Expecting people dig through a convoluted process just to figure out if the email is even relevant to them is just ridiculous.

Troubles with triaging syzbot reports

Posted Dec 16, 2022 19:19 UTC (Fri) by Wol (subscriber, #4433) [Link]

My reaction to that is to dump it in /dev/null. I have enough things to do anyway, it's easy to not find time to go searching down a rabbit warren.

And if it's work, I just dash off a reply saying "please provide the following extra info ..." - if I don't get a response it just disappears down the priorities :-) And if I do get a response well, once you've actually got buy-in from the other end, things usually end up well :-)

Cheers,
Wol


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds