Hi, On Sun, Aug 23, 2026 at 12:04:15PM +0200, Abdon wrote: > Package: src:linux > Version: 7.1.8-1~bpo13+1 > Severity: important > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > Comparing /boot/config-* across recent backports (trixie) kernels: > > linux-image-7.1.3+deb13-amd64: CONFIG_NTFS3_FS=m (modern driver > present) > linux-image-7.1.7+deb13-amd64: CONFIG_NTFS3_FS not set, CONFIG_NTFS_FS=m > instead > linux-image-7.1.8+deb13-amd64: same as 7.1.7 > > This looks like a regression: the modern ntfs3 driver (read/write, actively > maintained, enabled after the fix for #998627/#1000697) was replaced by the > legacy ntfs.ko driver (largely unmaintained, limited write support) between > 7.1.3 and 7.1.7/7.1.8.
One correction, this is not true, it is not the legacy implementation. NTFS3 has actually become poorly maintined after it got accepted and the ntfs driver itself was revamped completely and is a new implementation, see https://kernelnewbies.org/Linux_7.1#New_NTFS_implementation As Chris pointed out this will still have an impact on util-linux as well, so we have to decide if the change should be rolled back for the bpo kernels specifically and continue to ship ntfs3 as long it exists in the kernel (though it has as well important yet unadressed issues), or e.g. ntfs driver should get an alias for ntfs3 if ntfs3 is not enabled or another solution needs to be implemented. Regards, Salvatore
