Konstantin, can you answer?
On 2025/08/11 22:50, Christian Brauner wrote:
>> Is it possible to handle this problem on the NTFS3 side?
>
> Ugh, this is annoying.
> @Konstantin, why do you leave a zero mode for these files?
> Let's just make them regular files?
>
>>
>> --- a/fs/ntfs3/inode.c
>> +++ b/fs/ntfs3/inode.c
>> @@ -470,8 +470,9 @@ static struct inode *ntfs_read_mft(struct inode *inode,
>> } else if (fname && fname->home.low == cpu_to_le32(MFT_REC_EXTEND) &&
>> fname->home.seq == cpu_to_le16(MFT_REC_EXTEND)) {
>> /* Records in $Extend are not a files or general directories. */
>> inode->i_op = &ntfs_file_inode_operations;
>> + mode = S_IFREG;
>> } else {
>> err = -EINVAL;
>> goto out;
>> }
>>
>> I don't know what breaks if we pretend as if S_IFREG...
