mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>,
	Namjae Jeon <linkinjeon@kernel.org>
Cc: Hyunchul Lee <hyc.lee@gmail.com>,
	ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
	Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH 1/2] ntfs: do not read ahead encrypted files
Date: Mon, 12 Oct 2026 16:49:10 +0800	[thread overview]
Message-ID: <e590b551-b021-4ec7-b769-aad43fe6ac1c@163.com> (raw)
In-Reply-To: <20261012062040.3826828-2-zhanxusheng@xiaomi.com>



在 2026/10/12 14:20, Zhan Xusheng 写道:
> From: Zhan Xusheng <zhanxusheng@xiaomi.com>
> 
> ntfs_read_folio() refuses EFS-encrypted files with -EOPNOTSUPP because
> decryption is not implemented.  ntfs_readahead() has no NInoEncrypted()
> test and passes them to iomap_readahead(), which maps the runlist and
> fills the folios with the raw on-disk ciphertext.  The folios are
> marked uptodate, so the read that follows never reaches ->read_folio
> and returns ciphertext instead of -EOPNOTSUPP.
> 
> ntfs_read_locked_inode() sets NInoEncrypted() and NInoNonResident() for
> a non-resident encrypted $DATA attribute and rejects the
> encrypted-and-compressed combination, so none of the three existing
> conditions fires.  read(), mmap(), splice() and fadvise() all populate
> the page cache through readahead.
> 
> Skipping readahead leaves the folio unpopulated, so the read falls back
> to ntfs_read_folio() and gets the intended error.
> 
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> Fixes: b041ca562526 ("ntfs: update iomap and address space operations")
> ---
>   fs/ntfs/aops.c | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/ntfs/aops.c b/fs/ntfs/aops.c
> index 517d9a1563e7d..ad781674fef1a 100644
> --- a/fs/ntfs/aops.c
> +++ b/fs/ntfs/aops.c
> @@ -240,10 +240,11 @@ static void ntfs_readahead(struct readahead_control *rac)
>   	};
>   
>   	/*
> -	 * Resident files are not cached in the page cache,
> -	 * and readahead is not implemented for compressed files.
> +	 * Resident files are not cached in the page cache, readahead is not
> +	 * implemented for compressed files, and ntfs_read_folio() refuses
> +	 * encrypted files because decryption is not implemented.
>   	 */
> -	if (!NInoNonResident(ni) || NInoCompressed(ni) ||
> +	if (!NInoNonResident(ni) || NInoEncrypted(ni) || NInoCompressed(ni) ||
>   	    NInoWofCompressed(ni))
>   		return;
>   	iomap_readahead(&ntfs_read_iomap_ops, &ctx, NULL);

Looks good to me.

Reviewed-by: Baolin Liu <liubaolin@kylinos.cn>


  reply	other threads:[~2026-10-12  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  6:20 [PATCH 0/2] ntfs: enforce the encrypted-file policy on the read paths Zhan Xusheng
2026-10-12  6:20 ` [PATCH 1/2] ntfs: do not read ahead encrypted files Zhan Xusheng
2026-10-12  8:49   ` liubaolin [this message]
2026-10-12  6:20 ` [PATCH 2/2] ntfs: reject direct I/O reads of " Zhan Xusheng
2026-10-12  8:49   ` liubaolin
2026-10-12  8:50 ` [PATCH 0/2] ntfs: enforce the encrypted-file policy on the read paths liubaolin
2026-10-12 10:01 ` Hyunchul Lee
2026-10-12 11:58 ` Namjae Jeon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e590b551-b021-4ec7-b769-aad43fe6ac1c@163.com \
    --to=liubaolin12138@163.com \
    --cc=hyc.lee@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs@lists.linux.dev \
    --cc=zhanxusheng1024@gmail.com \
    --cc=zhanxusheng@xiaomi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®