Linux 3.0 Release Delayed 187
JustinRLynn writes "A recent Google+ Post by Linus Torvalds indicates that version 3.0 of the Linux kernel will have to wait due to the discovery of a 'subtle pathname lookup bug.' Linus indicates, 'We have a patch, we understand the problem, and it looks ObviouslyCorrect(tm), but I don't think I want to release 3.0 just a couple of hours after applying it.'"
Re:Path names? Bah. (Score:5, Informative)
Re:Fair Enough (Score:3, Informative)
I don't know what commercial environment you've been in, but in the places I've worked, release becomes hell because you have your bug list and someone (read a commitee) has gone through and labeled the "show stoppers" which are bugs deemed important enough to be fixed before the software can be released, and because of politics in the commitee, all but the most trivial become show stoppers. Upon fixing the last show stopper, the software then needs to go through regression at a minimum, and usually a complete test suite before it's allowed to be released. And even then, that goes into system integration, where the whole process starts again.
Here's what the bug was! (Score:5, Informative)
Sadly, I don't understand the explanation or what the patch changes.
https://lkml.org/lkml/2011/7/17/103
Here's what the bug was! (Score:5, Informative)
https://lkml.org/lkml/2011/7/17/103 [lkml.org]
[Posted by Theovon earlier, but I prefer a clickable link.]
Re:Here's what the bug was! (Score:5, Informative)
Ok, from my reading of the patch which could be WAY the fuck wrong BTW, I think it is a race condition between the unlinking of a file and returning the inode to the pool AND the CP command ( copy a file ) traversing the inode list. In other words the CP command was trying to stat a file that was partially unlinked do to the update of the node list still being in progress.
If you still don't understand that don't feel bad, I had to read and re-read the note like 10 times before I probably got this explanation wrong.
Re:Google+ is still in testing too (Score:4, Informative)
He opted in by commenting on the post. Keeping everyone that is a part of a discussion "in the loop" is consistent with the purpose of social networking.
It isn't Google's fault that jampola chose to reply to a post which received a high signal-to-noise ratio.
Re:Linus Torvalds and Google+ (Score:3, Informative)
Recently.