Kluas

Could you please share more detail about why you think 6.1.63 is affected? As I can see in the links you have shared, the problematic commit was introduced in 6.1.64. So 6.1.63 is not affected. Am I missing something?

Most of the Armbian kernels are made by taking the upstream kernel and applying patches on top of it.
 
If you go to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/fs/ext4/file.c?h=v6.1.66, you will see that the commit at the top is the one that caused the bug. In the same url, if you change the version to 6.1.63, you can see the commit is not there. Hence we are not affected.
 
Fun Fact, first commit after we had made v23.11 release was upgrading to 6.1.64 kernel, and it was only published to beta repository. Currently beta repository is using 6.1.66 kernel for current branch. 

To my understanding it was introduced by kernel commit 91562895f803, which was accepted by kernel team
https://lore.kernel.org/linux-ext4/87bkbbijwt.fsf@doe.com/T/
 
I didn't find any changelogs for the kernel on my Armbian host. I looked into these changelogs, but didn't find any data:
  zless /usr/share/doc/linux-dtb-current-meson64/changelog.gz
  zless /usr/share/doc/linux-image-current-meson64/changelog.gz
--> I'm unsure, if I'm affected. FUD.,
 
On the other side, on the Debian Users ML are reports, that Debian Bookworm is affected:
https://lists.debian.org/debian-user/2023/12/msg00500.html
More FUD on my site.
 
As I don't have a changelog, and people are saying that my distribution (bookworm) is affected, I can only assume that Armbian is very likely affected too.

But I'm glad to here, that I'm not.
Thank you.