On Fri, 31 Jul 2015, Daniel Phillips wrote:
On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote:
We, the Linux Community have less tolerance for losing people's data and
preventing them from operating than we used to when it was all tinkerer's
personal data and secondary systems.
So rather than pushing optimizations out to everyone and seeing what
breaks, we now do more testing and checking for failures before pushing
things out.
By the way, I am curious about whose data you think will get lost
as a result of pushing out Tux3 with a possible theoretical bug
in a wildly improbable scenario that has not actually been
described with sufficient specificity to falsify, let alone
demonstrated.
you weren't asking about any particular feature of Tux, you were asking if we
were still willing to push out stuff that breaks for users and fix it later.
Especially for filesystems that can loose the data of whoever is using it, the
answer seems to be a clear no.
there may be bugs in what's pushed out that we don't know about. But we don't
push out potential data corruption bugs that we do know about (or think we do)
so if you think this should be pushed out with this known corner case that's not
handled properly, you have to convince people that it's _so_ improbable that
they shouldn't care about it.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
