When discussing the other day Published 27 edition of the patches set with the implementation of the NTFS file system from Paragon Software, Linus Torvalds told that does not see Obstacles for receiving this set of patches into the next change window. If there is no unforeseen problems, the NTFS support from Paragon Software will be included in the kernel 5.15, the release of which is expected in November.
During the speech remaining before the adoption of the patch, Linus recommended to double-check the correctness of signature signature signature in patches confirming authorship over the transmitted code and the readiness of its propagation as part of the nucleus under a free license. Paragon Software also recommended to make sure that the legal department is aware of all the consequences of the transmission of code under the GPLv2 license and understands the essence of this kick-flying license.
The new NTFS driver code was opened by Paragon Software in August last year and is different from the driver’s core in the recording mode already in the driver’s kernel. The old driver has not been updated for many years and is in a deplorable state. The new driver supports all the capabilities of the current version of NTFS 3.1, including extended file attributes, data compression mode, efficient operation with emptiness in files and play changes from the journal to restore integrity after failures.
In 27 patches, Paragon Software has adapted the driver to change in the IOV API, replacing the ov_iter_copy_from_user_atomic () call to Copy_Page_From_iter_atomic ()
And stop using the ov_iter_advance () function. Of the recommendations expressed in the discussion, it remains intelligent translation code for using FS / IOMAP, but this is not a mandatory requirement, but only a recommendation that can be implemented after inclusion in the kernel. In addition, Paragon Software confirmed that it was ready to accompany the proposed code in the kernel and plans to further translate the implementation of journaling on top of the Journaling Block Device universal block device in the core, on the basis of which journaling in EXT3, EXT4 and OCFS2 is organized.