4 ms·
so everything before 6.1 is ok, and after 6.5 is also ok?
by jeroen79 3y ago
so everything before 6.1 is ok, and after 6.5 is also ok?
- altairprime 3y ago6.1.64+ affected, per reply on thread.
- kvemkon 3y agoShould be fixed in 6.1.66. iomap: update ki_pos a little later in iomap_dio_complete https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=ea574927fc0bc343016ea3337fcfc0b3fb26fe08 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux...
- csdvrx 3y agoIs what you've linked the patch that should be backported to affected kernels? As the potentially problematic patch causing the corruption, I found https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=91562895f803 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux... but it's not present in the 6.2.2 I run. I'm very conservative in the versions or critical components like kernels or dkms modules, that didn't protect me against the ZFS bug, but it seems to have avoided me this EXT4 bug!
- pixl97 3y ago>The commit got merged in 6.5-rc1 so all stable kernels that have 91562895f803 ("ext4: properly sync file size update after O_SYNC direct IO") before 6.5 are corrupting data - I've noticed at least 6.1 is still carrying the problematic commit. Greg, please take out the commit from all stable kernels before 6.5 as soon as possible, we'll figure out proper backport once user data are not being corrupted anymore. Thanks!
- spyc 3y agoThe way I read https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/ https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuh... 6.5+ should be okay. PS: Please correct me if not!