linux-kernel - [FS-DEV][NTFSPLUS][BUGREPORT]NtfsPlus extend mft data allocation error.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <OcRf3_Q--F-9@tutamail.com>
Date: Sat, 25 Oct 2025 20:40:45 +0200 (GMT+02:00)
From: craftfever@...amail.com
To: Linkinjeon <linkinjeon@...nel.org>
Cc: Linux Fsdevel <linux-fsdevel@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Iamjoonsoo Kim <iamjoonsoo.kim@....com>,
	Cheol Lee <cheol.lee@....com>, Jay Sim <jay.sim@....com>,
	Gunho Lee <gunho.lee@....com>
Subject: [FS-DEV][NTFSPLUS][BUGREPORT]NtfsPlus extend mft data allocation
 error.

Hi, I' decided to test your new driver, as I found ntfs3 driver buggy and causing system crush under huge amount of files writing ti disk ("I'm reported this bug already on lore.kernel maillists). The thing is ntfsplus demonstrated buggy behavior in somewhat similar situation, but without system crushing or partition corruption. When I try, for example, download many small files through download manager, download can interrupt, and cosole version writes about memory allocation error. Similar error was in ntfs3 driver, but in this case with ntfsplus there is no program/system crash, just soft-erroring and interrupting, but files cannot be wrote in this case. In dmesg this errors follow up with this messages:

[16952.870880] ntfsplus: (device sdc1): ntfs_mft_record_alloc(): Failed to extend mft data allocation.
[16954.299230] ntfsplus: (device sdc1): ntfs_mft_data_extend_allocation_nolock(): Not enough space in this mft record to accommodate extended mft data attribute extent.  Cannot handle this yet.

I know. that driver in development now, so I'm reporting this bug in time when development is still in process. Thank you