Troubles with triaging syzbot reports [LWN.net]

Troubles with triaging syzbot reports

Posted Dec 15, 2022 1:24 UTC (Thu) by viro (subscriber, #7872)
In reply to: Troubles with triaging syzbot reports by NYKevin
Parent article: Troubles with triaging syzbot reports

FWIW, he's not in the syzkaller git logs. And for the record, I don't think that anyone with that attitude ("the Most Holy Tool is an unparalleled blessing upon humanity; only a vile ingrate could possibly find any of its aspects deficient!!!") could be involved in the development of the tool in question. Cheerleading? Sure. Making the actual developers cringe? You bet. Contributing? Not likely.

Marco Elver is one of the syzkaller developers, so's Alexander Potapenko. AFAICS, nobody else in that thread is.

Hillf sounds like a Team OS/2 refugee or an Amiga fanboy on a bad flashback, TBH...

to post comments

Troubles with triaging syzbot reports

Posted Dec 15, 2022 5:48 UTC (Thu) by NYKevin (subscriber, #129325) [Link]

> And for the record, I don't think that anyone with that attitude ("the Most Holy Tool is an unparalleled blessing upon humanity; only a vile ingrate could possibly find any of its aspects deficient!!!") could be involved in the development of the tool in question.

You'd be surprised. I've encountered quite a few (secondhand) horror stories of upstreams behaving in exactly that fashion.

(My usual attitude towards these kinds of disputes tends to look pro-upstream, but it's really more pro-the-people-who-do-the-work-call-the-shots; if upstream doesn't want to make a change, they don't have to, but neither does downstream have to use/package/triage/etc. upstream's work. It would obviously be preferable if everyone got along.)