Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like...
by X86BSD on Saturday August 06, 2016 @12:55AM
(#12237078)
Waiting to implement a feature while you actually engineer it well and robustly is not the same as throwing poop at a wall and seeing what sticks then scraping the poop off and forming it into another shape and throwing at the wall again.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like...
by vidoc on Saturday August 06, 2016 @01:14AM
(#12237137)
Seems like you are no fan of linux's robust mutexes implementation. Sincerely, you probably know more than me about the implementation and I'd be curious to have your take on it as I have not looked at how (and so late) it was implemented in FreeBSD.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like...
by X86BSD on Saturday August 06, 2016 @01:28AM
(#12237171)
These are great reads for how it was implemented. As for how late see above.
https://www.bsdcan.org/2012/schedule/attachments/195_locking...
https://books.google.com/books?id=aY1pBAAAQBAJ&printsec=fron...
Well in this particular case, seems like this feature was added in linux 2.6.2 (2004). epoll itself was added in linux 2.5.44 (2002), so yep, you're correct that they didn't make this right immediately. Now I think it is rather easy to play this game of pinpointing flaws this way and it could be done the other way around, probably in an equally as unconstructive matter (e.g: how long did freebsd wait for robust mutexes?).
That said, amazing speaker, thanks for the links.