I have to agree, it's probably a symptom of less-than-stellar kernel testing procedures. Everyone just sends patches, hopefully tested well enough, then the guys on higher levels of the commit hierarchy take a look at the code, and finally Linus says "just a usual release, some changes here some changes there, please test" and then it's released eventually.
So no formal testing, just random people who may or may not use different features of the development kernel and if there are no complaints after some time, it goes public as a "stable" release. Not very convincing.
Some time ago I was unsure if I should really use BTRFS raid1 for my file server. I almost decided to use ext4 raid1 instead. Is ext4 on a raid1 volume affected by this bug? If so, I'm glad I use BTRFS ? the checksum feature appeared to be worth it.
So no formal testing, just random people who may or may not use different features of the development kernel and if there are no complaints after some time, it goes public as a "stable" release. Not very convincing.
Some time ago I was unsure if I should really use BTRFS raid1 for my file server. I almost decided to use ext4 raid1 instead. Is ext4 on a raid1 volume affected by this bug? If so, I'm glad I use BTRFS ? the checksum feature appeared to be worth it.
Comment