Re: [PATCH v1] ntfs: fix lookup of POSIX names with Windows-invalid characters

From: Namjae Jeon

Date: Sat Sep 12 2026 - 22:54:11 EST


> Hi Namjae and Hyunchul,
Hi Baolin,
>
> Hyunchul, I noticed that the patch you posted in GitHub issue #87 had
> not yet been sent to the mailing list, so I assumed you might not have
> had time to send it.
>
> I am helping submit your patch. I preserved your authorship and
> Signed-off-by line, and added only my Tested-by trailer:
>
> Tested-by: Baolin Liu <liubaolin@xxxxxxxxxx>
Thanks for the test and sending the patch to the list instead of Hyunchul!
>
> I applied the patch on top of commit 9a05b5715cfa("ntfs: remove
> unreachable code in load_and_init_attrdef/upcase"),which was the latest
> commit on the ntfs-next branch when I performed the tests.
>
> After applying the patch, I successfully built a kernel with the
> legacy NTFS driver built in. I then booted this kernel in QEMU and
> tested it using an NTFS test image.
>
> In a small directory, I tested the following filenames:
> 1. The complete filename reported in issue #87
> 2. question?mark
> 3. asterisk*mark
> 4. less<than
> 5. greater>than
> 6. double"quote
>
> For each filename, I created the file, ran sync, dropped the
> page,inode, and dentry caches, read the file again to verify lookup
> after reload, deleted it, and confirmed that it no longer existed.
>
> I also created 1000 filler files to exercise the large-directory
> lookup path. In that directory, middle?entry was created, read
> successfully after dropping the caches, and deleted successfully.
>
> All the tests above passed. The kernel log contained
> neither"Collation error" nor "Delete failed".
Thanks, I will check it.
>
> Namjae and Hyunchul, if you need any assistance with further work, I
> would be very happy to help.
Thank you very much for your active participation in NTFS development!

Can you work 64bit cluster support for ntfs if you have the room?
Since this is not urgent, please feel free to work on it without
feeling pressured.

Thanks!