2 ms·
I reported it along with a few other users in https://marc.info/?l=linux-nilfs&m=157540765215806&w=2 https://marc.info/?l=linux-nilfs&m=157540765215806&w=2. I t
by Volundr 4y ago
I reported it along with a few other users in https://marc.info/?l=linux-nilfs&m=157540765215806&w=2 https://marc.info/?l=linux-nilfs&m=157540765215806&w=2. I think it just isn't widely enough used that Linus noticed we were broken. If I recall correctly it also wasn't directly fixed so much as incidentally. I just kept checking new kernel versions as they were released until one worked. There was never anything in the change-log (that I recall) about fixing the bug, just another change that happened to fix the issue.
Edit: Looking through the archives, it looks like my memory was somewhat uncharitable. It was reported in November and directly patched in June (https://marc.info/?l=linux-nilfs&m=159154670627428&w=2 https://marc.info/?l=linux-nilfs&m=159154670627428&w=2) so about 7 months after reporting. Not sure what kernel release that would've landed in, so could've been closer to 8.