linux-kernel - Re: [PATCH v1 1/3] mm/secretmem: fix GUP-fast succeeding on secretmem folios

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: <414cb2da-52c1-4f4f-9dcf-986f7aaccb0a@redhat.com>
Date: Tue, 26 Mar 2024 14:23:37 +0100
From: David Hildenbrand <david@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 Mike Rapoport <rppt@...nel.org>, Miklos Szeredi <mszeredi@...hat.com>,
 Lorenzo Stoakes <lstoakes@...il.com>, xingwei lee <xrivendell7@...il.com>,
 yue sun <samsun1006219@...il.com>, Miklos Szeredi <miklos@...redi.hu>,
 stable@...r.kernel.org
Subject: Re: [PATCH v1 1/3] mm/secretmem: fix GUP-fast succeeding on secretmem
 folios

On 25.03.24 19:30, Andrew Morton wrote:
> On Mon, 25 Mar 2024 14:41:12 +0100 David Hildenbrand <david@...hat.com> wrote:
> 
>> folio_is_secretmem() states that secretmem folios cannot be LRU folios:
>> so we may only exit early if we find an LRU folio. Yet, we exit early if
>> we find a folio that is not a secretmem folio.
>>
>> ...
>>
>> Cc: <stable@...r.kernel.org>
> 
> Thanks, I split up this series.  Because this patch goes
> mm-hotfixes-unstable -> mm-hotfixes-stable -> mainline whereas the
> other two go mm-unstable -> mm-stable -> mainline at a later time.

Makes sense. I'll resend a v2 later, because there are some major 
changes (the fix was wrong/incomplete, we have to remove the LRU test 
completely).

-- 
Cheers,

David / dhildenb