News for hackers. Stuff that matters.
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor... by mixedCase on Tuesday July 05, 2022 @04:24PM (#31993234)
Have never used those APIs, but I would assume it'd happen if drivers fail to implement basic API promises and PulseAudio doesn't code defensively against those kind of bugs.
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor... by vintermann on Tuesday July 05, 2022 @04:42PM (#31993436)
If drivers fail that disastrously to implement the APIs they say they implement, how did they end up in distributors' kernel trees?
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor... by ElectricalUnion on Tuesday July 05, 2022 @04:49PM (#31993512)
They were deemed "good enough" when all you were using was basic, simple OSS. Not when you're attempting to use all the capabilities of ALSA.
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor... by robonerd on Wednesday July 06, 2022 @02:25PM (#32004841)
> PulseAudio doesn't code defensively against those kind of bugs.

That's a reoccurring pattern across Lennart software. He gets an idea of the way things should work, maybe from the spec or maybe just from his own subjective biases, and has his software expect things to work that way and fail when it doesn't. Every time, he'll say it's the other guys fault. Sometimes his software even fails unsafe and he still blames everybody else.

The '0day' username bug in systemd exemplifies this. Lennart decided that usernames beginning with numbers weren't valid, even though Linux permits it. Systemd was found to run service files with User=0day specified as root instead, not as the user 0day. To Lennart this was not a bug because in his subjective opinion the rest of the system was in error for permitting a username beginning with a number. Even if he were right that usernames beginning with numbers shouldn't be valid, the mere fact that they can occur is reason enough to code defensively around it. At the very least systemd could fail safe when it encounters such an 'invalid' username. But no, he thought there was nothing wrong with failing-to-root. It was everybody else's fault, of course.

https://lwn.net/Articles/727490/

https://github.com/systemd/systemd/issues/6237#issuecomment-...