linux-kernel - Re: [RFC PATCH] block, fs: use FOLL_LONGTERM as gup

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z8m-vJ6mP1Sh2pt3@infradead.org>
Date: Thu, 6 Mar 2025 07:26:52 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Sooyong Suk <s.suk@...sung.com>
Cc: viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, linux-mm@...ck.org,
	jaewon31.kim@...il.com, spssyr@...il.com
Subject: Re: [RFC PATCH] block, fs: use FOLL_LONGTERM as gup_flags for direct
 IO

On Thu, Mar 06, 2025 at 04:40:56PM +0900, Sooyong Suk wrote:
> There are GUP references to pages that are serving as direct IO buffers.
> Those pages can be allocated from CMA pageblocks despite they can be
> pinned until the DIO is completed.

direct I/O is eactly the case that is not FOLL_LONGTERM and one of
the reasons to even have the flag.  So big fat no to this.

You also completely failed to address the relevant mailinglist and
maintainers.