Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, upstream has now completely removed the old classic NTFS driver. And ntfs3 has been setup to serve as alias to the old one: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/ntfs3?id=74871791ffa9562d43567c5ff2ae93def3f39f65 Are there still concerns to enable it by default? And if so which ones? Regards Felix
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hey. Seems there were at least a series of commits from upstream last November and few again this January. And there even seem to be some more in their dev branch. The number of CVEs mentioned by Salvatore is worrying, but it looks even much worse over the years for ntfs-3g: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ntfs-3g Plus it seems ntfs-3g upstream is even less active than ntfs3's: https://github.com/tuxera/ntfs-3g/ Last commit June 2023. Of course this could also just mean that ntfs-3g is simply more mature and less issues are found - dunno. Security-wise the same, could mean that they've no ironed out all issues, or simply no-one looks at it anymore. What I did notice in this bug is that quite some people pushed for enabling it, with email addresses that look in style similar to those that where used in the XZ social engineering or like throw away addresses. Cheers, Chris.
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hey folks, just to chime in. I had been using the commercial driver from Paragon without issues _before_. I switched some of my machines to Manjaro and and kernel 6.6. So I "had" to switch to ntfs3, given their commercial driver won't build against the 6.6 kernel. Boy, was I surprised to find that the ntfs3 driver corrupted a partition (see forum thread here: https://forum.manjaro.org/t/re-ntfs3-keeps-corrupting-my-ntfs-partitons/157736). Nothing that their _commercial_ chkntfs wasn't able to repair (the userland tools work, but their commercial driver lags behind in terms of linking to the latest kernels), but that's: DATA CORRUPTION. Performance in terms of speed is nice to have, but data integrity is a more important performance feature for a file system; at least in my book. So, my confidence in the ntfs3 driver has been shattered for now, I have to admit. I had in the past used the commercial Paragon driver on some of my machines, but ntfs-3g where ever I didn't have a license. So I have worked with both before. The better tool support from Paragon and the performance improvement were the main selling points to me, compared to ntfs-3g. I never encountered data corruption with the commercial driver or ntfs-3g. But the ntfs3 driver evidently has such issues. And while those quoted threads are old, I think there is more recent evidence that there are issues ... Citing the stability of their commercial driver makes no sense, by the way. They don't share the same lineage. Their Linux driver is - according to them - a rewrite, whereas the commercial one traces its roots to NTFS for DOS. In light of my experiences with ntfs3, I can understand Salvatore's skepticism towards that driver. Just my two cents, Viðarr PS: the only thing that can be said in favor of enabling the driver would be that it enables a larger user base to test it and weed out issues. But I wouldn't call its current state stable or robust, given my experiences and those that turned up in web searches once I started to look for solutions.
Bug#998627:
On Sat, 17 Feb 2024 22:38:57 +0800 an xiao > Hello, > > Paragon-software is active enough on their subsystem, > and NTFS3 is extremely stable now. > Please consider enabling the NTFS3 driver for sid. > > Thinks and best regards, > Littlewhite Hi, today was a pull request submitted which removes the old ntfs driver from kernel [1]. Ok it's not enabled in Debian. But it also says that ntfs3 is a full replacement and that Archlinux has enabled it since 5.15 Would be nice to have it enabled in Debian too. TIA Felix [1] https://lore.kernel.org/lkml/20240308-vfs-ntfs-ede727d2a142@brauner/
Bug#998627:
On Wed, 14 Jun 2023 09:18:05 +0200 Salvatore Bonaccorso wrote: > Hi, > > On Wed, Jun 14, 2023 at 08:41:29AM +0200, BW wrote: > > Is NTFS3 still not available, not even in Debian 12? After so long? > > Please don't be patronizing and think you now better than the users and > > decide what they need and don't. > > This is Linux, users are capable of deciding if this is useable for them or > > not. > > I don't think any will use NTFS as a production file-system on Linux! So > > don't use any excuse of missing utils or it is not stable. NTFS-3G is not > > stable and useable as production FS either. > > NTFS3 will for the huge majority of users be used in a utility-context, > > e.g. accessing/grapping files from a disk from a MS box etc. > > Please make it available > > No it is not available even in Debian 12; Unless paragon-software show > to be active more on their subsystem. Or let's say "maybe for trixie > it will be made available at some point". With a highlight on "maybe". > > There is not enough confidence that it is well maintained upstream. > Additionally a stream of CVEs would have affected bookworm if we would > have enabled it. So, while not written in stone, it was the right > decision to not enable it for Debian 12. > > https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ntfs3 (gives a rough > overview) > > And the story around fs/ntfs* and Debian requiring to mark it as > broken (cf. > https://salsa.debian.org/kernel-team/linux/commit/becaca2c809a9c8eeb45287d3ecc5c572cc49733 ) > should not be needed to be repeated. > > Regards, > Salvatore > > Hello, Paragon-software is active enough on their subsystem, and NTFS3 is extremely stable now. Please consider enabling the NTFS3 driver for sid. Thinks and best regards, Littlewhite
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Package: linux Followup-For: Bug #998627 Dear Maintainer, Please consider enabling the NTFS3 driver for debian-testing, so that it receives more test coverage before debian 13 (trixie) is released as stable. Thank you. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#998627: Come on!
Hi, On Wed, Jun 14, 2023 at 08:41:29AM +0200, BW wrote: > Is NTFS3 still not available, not even in Debian 12? After so long? > Please don't be patronizing and think you now better than the users and > decide what they need and don't. > This is Linux, users are capable of deciding if this is useable for them or > not. > I don't think any will use NTFS as a production file-system on Linux! So > don't use any excuse of missing utils or it is not stable. NTFS-3G is not > stable and useable as production FS either. > NTFS3 will for the huge majority of users be used in a utility-context, > e.g. accessing/grapping files from a disk from a MS box etc. > Please make it available No it is not available even in Debian 12; Unless paragon-software show to be active more on their subsystem. Or let's say "maybe for trixie it will be made available at some point". With a highlight on "maybe". There is not enough confidence that it is well maintained upstream. Additionally a stream of CVEs would have affected bookworm if we would have enabled it. So, while not written in stone, it was the right decision to not enable it for Debian 12. https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ntfs3 (gives a rough overview) And the story around fs/ntfs* and Debian requiring to mark it as broken (cf. https://salsa.debian.org/kernel-team/linux/commit/becaca2c809a9c8eeb45287d3ecc5c572cc49733) should not be needed to be repeated. Regards, Salvatore
Bug#998627: Come on!
Is NTFS3 still not available, not even in Debian 12? After so long? Please don't be patronizing and think you now better than the users and decide what they need and don't. This is Linux, users are capable of deciding if this is useable for them or not. I don't think any will use NTFS as a production file-system on Linux! So don't use any excuse of missing utils or it is not stable. NTFS-3G is not stable and useable as production FS either. NTFS3 will for the huge majority of users be used in a utility-context, e.g. accessing/grapping files from a disk from a MS box etc. Please make it available
Bug#998627:
On Fri, 20 Jan 2023, 06:52 Salvatore Bonaccorso, wrote: > Hi Norbert, > > On Thu, Jan 19, 2023 at 11:44:47PM +0100, Norbert Lange wrote: > > It's been ages, why isn't this enabled by now? How should this driver > > mature when no one can test it (without going through the hassle if > > compiling the Kernel). > > Thanks for asking back. NTFS3 driver is still not in astate making it > confident it's wise to enable it for a stable release. > > > https://lore.kernel.org/ntfs3/784f82c4-de71-b8c3-afd6-468869a36...@paragon-software.com/T/#me2324a967514564949f7ebcf3f9a5965f66921bf > is an example (it took from august to now, until the fix landed in > mainline). > > I think thus the arguments from https://bugs.debian.org/998627#75 > still holds. > > Regards, > Salvatore Hello Salvatore, AFAIK kernels receive a ton of patches in distros, Backported and what not. Is it not possible to atleast build the module but either blacklist it or offer it in a separate package? If it's in a sorry state, then that would direct the complaints to the module, not to the configuration. Thanks for the quick response. Norbert
Bug#998627:
Hi Norbert, On Thu, Jan 19, 2023 at 11:44:47PM +0100, Norbert Lange wrote: > It's been ages, why isn't this enabled by now? How should this driver > mature when no one can test it (without going through the hassle if > compiling the Kernel). Thanks for asking back. NTFS3 driver is still not in astate making it confident it's wise to enable it for a stable release. https://lore.kernel.org/ntfs3/784f82c4-de71-b8c3-afd6-468869a36...@paragon-software.com/T/#me2324a967514564949f7ebcf3f9a5965f66921bf is an example (it took from august to now, until the fix landed in mainline). I think thus the arguments from https://bugs.debian.org/998627#75 still holds. Regards, Salvatore
Bug#998627:
It's been ages, why isn't this enabled by now? How should this driver mature when no one can test it (without going through the hassle if compiling the Kernel).
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
On Fri, 29 Apr 2022 22:27:27 +0200 Salvatore Bonaccorso wrote: In meanwhile the current state of NTFS3 driver has been discussed upstream starting in https://lore.kernel.org/lkml/da20d32b-5185-f40b-48b8-2986922d8...@stargateuniverse.net/ You're well aware that this discussion ENDED IN early _MAY 2022_ ?!? If your arguments repeatedly cite ancient statements their validity is at least questionable. In the meanwhile we are on Linux 6.0.12, and NTFS3 is still not enabled. Just to make it clear: enabling NTFS3 will NOT change any existing usage of ntfs3-ng, it just creates a new possibility to increase the performance of using ntfs3 partitions. I am glad that on my production server I have Arch Linux, which enabled NTFS3 in their kernel with 5.15.2, and it ist running performant and rock stable. I would appreciate to be able to use this driver also on my Debian Testing system, but am still waiting in vain for many months to see this come true. Jm2c Heinz
Bug#998627: sid enable
hello sid and teasting made for this purpose i suggest to enable it in sid at least and see where it goes Thanks Mina
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Sun, Mar 20, 2022 at 10:25:23PM +0100, Ben Hutchings wrote: > On Fri, 2022-03-18 at 20:58 +0100, lenni_na1 wrote: > > Hi, > > > > are there any news on this? > > > > We are now at kernel 5.16 in testing and as far as I can tell the ntfs3 > > driver still hasn't been enabled. > > The recent traffic on the ntfs3 list seems to consist of bug reports > and small fixes, none of them being addressed by the supposed > maintainer of the filesystem (who last posted at the end of November). > > I think that we would be doing our users a disservice by enabling ntfs3 > in this state. In meanwhile the current state of NTFS3 driver has been discussed upstream starting in https://lore.kernel.org/lkml/da20d32b-5185-f40b-48b8-2986922d8...@stargateuniverse.net/ . Regards, Salvatore
Bug#998627: Please enable ntfs3 module, it does not conflict wiht anything
Hi! I was just stumblinmg over this bugreport, and must say I am surprised at the logic here - the ntfs3 module does not conflict with existing filesystem drivers (such as ntfs-3g), so existing systems shouldn't be negatively affected as they would continue to either fail to mount or use ntfs-3g, if installed. also, the logic of keeping it out is very flawed, namely that the feature is new. but the code in question existed for a long time outside the kernel, so arguing there might possibly, potentially, maybe be some problems in the code (that haven't surfaced in the half a year since the release) is very strange. while I appreciate that the kernel package maintainers try to keep dangerous or broken modules disabled, I think doing so based on zero actual evidence is going to far, especially given that other broken modules are enabled (e.g. ufs, which does get used by default and can eat ufs filesystems for breakfast). the only actual evidence so far is that there is no working fsck - well, the same argument could be used to keep btrfs out of debian. I would have understood this decision if the ntfs3 module conflicted with the existing ntfs or ntfs-3g drivers, but it doesn't. please reconsider your decision - thanks!
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
On Fri, 2022-03-18 at 20:58 +0100, lenni_na1 wrote: > Hi, > > are there any news on this? > > We are now at kernel 5.16 in testing and as far as I can tell the ntfs3 > driver still hasn't been enabled. The recent traffic on the ntfs3 list seems to consist of bug reports and small fixes, none of them being addressed by the supposed maintainer of the filesystem (who last posted at the end of November). I think that we would be doing our users a disservice by enabling ntfs3 in this state. Ben. -- Ben Hutchings If the facts do not conform to your theory, they must be disposed of. signature.asc Description: This is a digitally signed message part
Bug#998627:
Hello, i'm trying to use the newer ntfs3 by Paragon on my 5.15.0-2 kernel but it is still not available as module. So i'm just typing some few words to make it available in future releases. Regards
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
On Tue, 23 Nov 2021 22:34:25 +0100 Salvatore Bonaccorso wrote: Are tools available to handle creation and checking of such NTFS3 filesystems? The last time I went to the paragon software site it mentioned it was planning. This is not a must, but kept me for slightly on the on hold position for enabling it. You mean you are holding back the DRIVER because you are missing USERSPACE utilities to handle and examine NTFS 3.1 filesystems?!? One has nothing to do with the other. There are a lot of NTFS utilities available with the ntfs-3g package, namely: mkntfs ntfscat ntfsclone ntfscluster ntfscmp ntfscp ntfsdecrypt ntfsfallocate ntfsfix ntfsinfo ntfslabel ntfsls ntfsrecover ntfsresize ntfssecaudit ntfstruncate ntfsundelete ntfswipe Nearly all of them (apart from ntfssecaudit cases) work on devices, not on mounted file systems, so the NTFS driver used is not in involved. An idea would be to split the ntfs-3g package into ntfs-3g-tools ntfs-3g-fusedriver libntfs-3g (on which the former depends) A Paragon donated mkfs.ntfs would be a nice thing, but mkntfs from ntfs-3g already fits for nearly all purposes. And I guess most people would want the new ntfs3 driver for filesystems created with Windows. On Sat, 27 Nov 2021 14:14:53 +0100 Salvatore Bonaccorso wrote: Apart from Ted Ts'o comments, I looked up the mailinglist, https://lore.kernel.org/ntfs3/ which relatively quiet. The same goes for commits in fs/ntfs3 in mainline, since the merge in 5.15 there ws almost no activity, which is slightly unusual for something new entering. Looking on the same mailinglist, I think they recently did a lot to fix the test issues and much more, as can be seen: [PATCH] ntfs3: Fix showing umask option 2021-11-27 13:51 UTC [PATCH 1/2] fs/ntfs3: clarify why $Extend init is being skipped 2021-11-26 12:04 UTC (2+ messages) [PATCH] Doc/fs/ntfs3: Fix a trivial typo 2021-11-26 11:52 UTC (2+ messages) [ramfs] 0858d7da8a: canonical_address#:#[##] 2021-11-26 11:36 UTC (2+ messages) [PATCH] fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()' 2021-11-23 15:47 UTC (2+ messages) Bug using new ntfs3 file system driver (5.15.2 on Arch Linux) 2021-11-19 14:19 UTC (3+ messages) No more accessible (compromised) NTFS volume 2021-11-16 17:16 UTC [PATCH v2 0/4] fs/ntfs3: Various fixes for xattr and files 2021-11-15 15:50 UTC (11+ messages) ` [PATCH 1/4] fs/ntfs3: Keep preallocated only if option prealloc enabled ` [PATCH 2/4] fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions ` [PATCH 3/4] fs/ntfs3: Update i_ctime when xattr is added ` [PATCH 4/4] fs/ntfs3: Optimize locking in ntfs_save_wsl_perm [BUG] Unable to mount NTFS drive, no error in dmesg 2021-11-11 4:39 UTC Readahead for compressed data 2021-10-29 6:15 UTC (16+ messages) [PATCH v2] checkpatch: Improve CVS revision marker check 2021-10-27 10:56 UTC [PATCH] checkpatch: Remove cvs keyword check 2021-10-27 9:21 UTC (4+ messages) [PATCH 0/4] fs/ntfs3: Various fixes for xfstests problems 2021-10-26 21:37 UTC (11+ messages) ` [PATCH 1/4] fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode if called from function ntfs_init_acl ` [PATCH 2/4] fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space) ` [PATCH 3/4] fs/ntfs3: Check new size for limits ` [PATCH 4/4] fs/ntfs3: Update valid size if -EIOCBQUEUED [PATCH] fs/ntfs3: clarify emitted log message when marking volumes as dirty 2021-10-26 20:56 UTC (3+ messages) [PATCH 2/2] fs/ntfs3: clarify emitted log message when marking volumes as dirty 2021-10-26 20:55 UTC [PATCH] fs/ntfs3: clarify why $Extend init is being skipped 2021-10-26 20:49 UTC (2+ messages) (very low importance) NTFS version message 2021-10-26 18:03 UTC (2+ messages) [PATCH 0/4] fs/ntfs3: Various fixes for xattr and files 2021-10-24 11:13 UTC (12+ messages) ` [PATCH 1/4] fs/ntfs3: Keep preallocated only if option prealloc enabled ` [PATCH 2/4] fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions ` [PATCH 3/4] fs/ntfs3: Optimize locking in ntfs_save_wsl_perm ` [PATCH 4/4] fs/ntfs3: Update i_ctime when xattr is added NTFS3: junctions are not properly resolved 2021-10-22 12:50 UTC [PATCH 0/2] Removing of old code 2021-10-19 17:11 UTC (4+ messages) ` [PATCH 1/2] fs/ntfs3: Remove unnecessary functions cleanup block device inode syncing 2021-10-19 13:54 UTC (14+ messages) ` [PATCH 1/7] fs: remove __sync_filesystem ` [PATCH 2/7] block: remove __sync_blockdev ` [PATCH 3/7] xen-blkback: use sync_blockdev ` [PATCH 4/7] btrfs: " ` [PATCH 5/7] fat: use sync_blockdev_nowait ` [PATCH 6/7] ntfs3: " ` [PATCH 7/7] block: simplify the block device syncing code don't use ->bd_inode to access the block device size v3 2021-10-19 1:04 UTC (40+ messages) ` [PATCH 01/30] block: move the SECTOR_SIZE related definitions to blk_types.h ` [PATCH 02/30] block: add a bdev_nr_bytes helper ` [PATCH 03/30] bcache: remove
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Wed, Nov 24, 2021 at 03:14:56PM +0800, Wenbin Lv wrote: > Hi, > > On Wed, Nov 24, 2021 at 5:36 AM Salvatore Bonaccorso > wrote: > > > > Hi, > > > > > > Are tools available to handle creation and checking of such NTFS3 > > filesystems? The last time I went to the paragon software site it > > mentioned it was planning. This is not a must, but kept me for > > slightly on the on hold position for enabling it. > > > > Regards, > > Salvatore > > > > Paragon only mentioned they are planning to release mkfs.ntfs in their > FAQ, not the fsck tool[1]. So we'll need ntfs-3g or Windows for fsck > anyway if they don't release it. Stability and further code > maintenance, however, are matters of greater concern as Ted Ts'o > pointed out[2]. Maybe we should hold it back for some time to see what > will happen. Yes right, the missing tools was not an argument against it, just an additional indication. As you pointed out is more concerning, and hinting that we should wait a bit more to see how it evolves. Apart from Ted Ts'o comments, I looked up the mailinglist, https://lore.kernel.org/ntfs3/ which relatively quiet. The same goes for commits in fs/ntfs3 in mainline, since the merge in 5.15 there ws almost no activity, which is slightly unusual for something new entering. Regards and thank you! Salvatore
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Wed, Nov 24, 2021 at 5:36 AM Salvatore Bonaccorso wrote: > > Hi, > > > Are tools available to handle creation and checking of such NTFS3 > filesystems? The last time I went to the paragon software site it > mentioned it was planning. This is not a must, but kept me for > slightly on the on hold position for enabling it. > > Regards, > Salvatore > Paragon only mentioned they are planning to release mkfs.ntfs in their FAQ, not the fsck tool[1]. So we'll need ntfs-3g or Windows for fsck anyway if they don't release it. Stability and further code maintenance, however, are matters of greater concern as Ted Ts'o pointed out[2]. Maybe we should hold it back for some time to see what will happen. Best regards, Wenbin Lv [1] https://www.paragon-software.com/home/ntfs3-driver-faq/ [2] https://lore.kernel.org/lkml/yqnhxiu+eaaxi...@mit.edu/
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Le 2021-11-23 22:34, Salvatore Bonaccorso a écrit : > Hi, > > On Tue, Nov 23, 2021 at 12:37:02PM +0100, Vincent Blut wrote: > > Hi, > > > > Le 2021-11-22 18:54, Boyuan Yang a écrit : > > > Hi, > > > > > > On Fri, 5 Nov 2021 16:55:33 +0800 Wenbin Lv wrote: > > > > Package: src:linux > > > > Version: 5.15-1~exp1 > > > > Severity: wishlist > > > > > > > > Hi, > > > > Paragon's NTFS3 driver has been merged to 5.15, and it offers much > > > > better performance compared to ntfs-3g. Currently it is not enabled in > > > > Debian's kernel config, nor can I mount NTFS partitions using '-t > > > > ntfs3'. > > > > Please enable it if you consider it stable enough. Thank you! > > > > > > Now that 5.15 has been uploaded to Unstable, this issue will attract wider > > > attention. Please consider enabling it in future uploads. > > > > I'll send a merge request to the kernel team later today. > > Are tools available to handle creation and checking of such NTFS3 > filesystems? Not yet AFAIK. > The last time I went to the paragon software site it mentioned it was > planning. This is not a must, but kept me for slightly on the on hold > position for enabling it. Understandable! Let's hold off for the moment then. > Regards, > Salvatore Cheers, Vincent signature.asc Description: PGP signature
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Tue, Nov 23, 2021 at 12:37:02PM +0100, Vincent Blut wrote: > Hi, > > Le 2021-11-22 18:54, Boyuan Yang a écrit : > > Hi, > > > > On Fri, 5 Nov 2021 16:55:33 +0800 Wenbin Lv wrote: > > > Package: src:linux > > > Version: 5.15-1~exp1 > > > Severity: wishlist > > > > > > Hi, > > > Paragon's NTFS3 driver has been merged to 5.15, and it offers much > > > better performance compared to ntfs-3g. Currently it is not enabled in > > > Debian's kernel config, nor can I mount NTFS partitions using '-t > > > ntfs3'. > > > Please enable it if you consider it stable enough. Thank you! > > > > Now that 5.15 has been uploaded to Unstable, this issue will attract wider > > attention. Please consider enabling it in future uploads. > > I'll send a merge request to the kernel team later today. Are tools available to handle creation and checking of such NTFS3 filesystems? The last time I went to the paragon software site it mentioned it was planning. This is not a must, but kept me for slightly on the on hold position for enabling it. Regards, Salvatore
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, Le 2021-11-22 18:54, Boyuan Yang a écrit : > Hi, > > On Fri, 5 Nov 2021 16:55:33 +0800 Wenbin Lv wrote: > > Package: src:linux > > Version: 5.15-1~exp1 > > Severity: wishlist > > > > Hi, > > Paragon's NTFS3 driver has been merged to 5.15, and it offers much > > better performance compared to ntfs-3g. Currently it is not enabled in > > Debian's kernel config, nor can I mount NTFS partitions using '-t > > ntfs3'. > > Please enable it if you consider it stable enough. Thank you! > > Now that 5.15 has been uploaded to Unstable, this issue will attract wider > attention. Please consider enabling it in future uploads. I'll send a merge request to the kernel team later today. > Thanks! > Boyuan Yang Have a good day, Vincent signature.asc Description: PGP signature
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Fri, 5 Nov 2021 16:55:33 +0800 Wenbin Lv wrote: > Package: src:linux > Version: 5.15-1~exp1 > Severity: wishlist > > Hi, > Paragon's NTFS3 driver has been merged to 5.15, and it offers much > better performance compared to ntfs-3g. Currently it is not enabled in > Debian's kernel config, nor can I mount NTFS partitions using '-t > ntfs3'. > Please enable it if you consider it stable enough. Thank you! Now that 5.15 has been uploaded to Unstable, this issue will attract wider attention. Please consider enabling it in future uploads. Thanks! Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Package: src:linux Version: 5.15-1~exp1 Severity: wishlist Hi, Paragon's NTFS3 driver has been merged to 5.15, and it offers much better performance compared to ntfs-3g. Currently it is not enabled in Debian's kernel config, nor can I mount NTFS partitions using '-t ntfs3'. Please enable it if you consider it stable enough. Thank you!
