Username or EmailPassword
With all due respect, it does not show persistence for the original developers, or much of anything good about them, really: any bug of this sort that's known about to cause data loss/corruption is generally considered a "no-ship" bug everywhere I've been, and this bug shows also that they simply didn't do very good testing and think about all the reasonably possible edge cases, and this existed for 25 years until some puzzled developer victimized by it tracked it down in a short time period. Kudos the developer that tracked this down: raspberries at the one(s) that should have caught and fixed this ages ago (how many generations does that count in when it comes to this field? ACK!)
Maybe you should try first to develop something like an operating system, then you should speak again. And now be calm, something professional is going on.
I understand how difficult it is to find every last single bug in a complex piece of software, but I still think it's a little odd how all the BSD devs are getting praised for fixing this bug like they are.
I mean, think about the kind of comments that would be here if it was a story about how Microsoft just fixed a 25 year old bug.
I'm pretty sure even Linux would get hammered, as people would come in claiming that the Linux devs spend too much time on new features without polishing the old ones, and someone would try to blame it on the unstable API.
Ah, shows you have absolutely no clue what I've developed in the past, or what I'm developing now:
1. Various CD premastering/analysis utilities, some multithreaded: a patent was involved with one project as I worked on the code for making CD+/CD-PLUS format (whatever they're calling it these days). Oh, that also involved me having to hack the Linux kernel because it wasn't setup to do what was needed previously.
2. Engine monitoring software for Cummins diesel engines from pickup-sized to ship engine-sized.
3. CNC/press brake software: yeah, I bet you'll have to look that up! Multithreading throughout, and oh yeah, if that's wrong, machinery is damaged and people may die, no exaggeration.
4. 3D CAD software: at least as complicated for all edge cases as an OS.
5. MPP cluster-based database running on linux, currently in use on smaller systems than what it'll be in a month or two, which is 1024 node system. Oh, yes, the database itself, not a "database application" and yes, it's at one of the big internet companies, and this database beats Oracle's best offerings for speed and running costs right now. I'm currently working as the white box QA engineer.
Before you have a clue what other people have done and have experience in, you really should think carefully. Fact of the matter is, this BSD bug has been there 25 years and was known by others. Sure, it's a multithreaded bug, but it isn't rocket science for this one, and it has been known about for several years before it was finally fixed, even though it was known to effectively lose data.
You seriously need to not assume things you don't have a clue about.
I think this illustrates the fallacy of the "many eyeballs" meme that is taken as the gospel truth in open source circles.
Here, we have a bunch of open source developers (samba) who find a flaw in an open source product (BSD) and instead of stepping through the BSD source tree to find the problem, they code a samba hack that works around the problem on BSDs. In fact, it appears they didn't even submit a bug report.
Guess what? This happens all the time in the closed source world. If we come across a bug in someone else's code, we code a temporary hack around the problem and wait for the bug to be resolved. This article suggests that such development culture appears in open source projects too, which is understandable.
I hope that naive open source advocates who keep preaching the "many eyeballs" meme will stop doing so. The majority of developers do not have the desire or the inclination to fix other peoples bugs even if the source is available. Hell, it seems that some don't even file bug reports...
So you're taking one specific incident, and using it to back up generalized statements about the whole Open Source community?
> I hope that naive open source advocates who keep preaching the "many
> eyeballs" meme will stop doing so. The majority of developers do not
> have the desire or the inclination to fix other peoples bugs even if the
> source is available. Hell, it seems that some don't even file bug
Just to show you another point of view: I have had that situation just a few days ago, where I would rather code around a bug in Eclipse IDE than report details or even fix it. Guess why? The bug had been known for more than three years, and repeatedly been marked as "we won't fix this, and we won't accept fixes" (for backwards compatibility).
No, I do not have the desire nor the inclination to investigate any deeper when I know that the aim of the developers is NOT to fix those bugs.
Well the test case was quite complex, wasn't it?
So I'm not surprised that this kind of things wasn't found early..
But the fact that Samba knew about this bug and that this wasn't fixed in the BSDs for several years is bad, yes.