From: David Hildenbrand <david@redhat.com>
To: Jann Horn <jannh@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Rik van Riel <riel@surriel.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Harry Yoo <harry.yoo@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/rmap: Add anon_vma lifetime debug check
Date: Fri, 25 Jul 2025 13:31:22 +0200 [thread overview]
Message-ID: <d6781e05-bde6-490c-af79-97993ed9018e@redhat.com> (raw)
In-Reply-To: <CAG48ez1=rd5W5SBAyyqu-=50AsRGg8pdYW5BZ4SFhHqFYOHbyg@mail.gmail.com>
On 25.07.25 13:24, Jann Horn wrote:
> On Fri, Jul 25, 2025 at 1:12 PM David Hildenbrand <david@redhat.com> wrote:
>> On 25.07.25 13:08, Jann Horn wrote:
>>> On Thu, Jul 24, 2025 at 11:56 PM David Hildenbrand <david@redhat.com> wrote:
>>>> 2) We have a folio here, so ... better
>>>>
>>>> if (folio_test_anon(folio) && !folio_test_ksm(folio)) {
>>>> ...
>>>> }
>>>
>>> Hrm, okay. It kind of irks me to write it as two checks when really I
>>> want to ask "is it this one specific type", but yeah, will change it.
>>
>> Well, ksm is a subtype of anon.
>
> I mean... not really? At least ksm folios are not a subtype of normal
> anon folios.
Well, what I mean is:
A KSM folio is considered an anon folio.
An anon folio is not necessarily a KSM folio.
Of course, there are implementation differences when it comes to
folio->mapping etc, just the way the rmap works.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-25 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 19:13 Jann Horn
2025-07-24 21:52 ` Andrew Morton
2025-07-25 10:59 ` Jann Horn
2025-07-24 21:56 ` David Hildenbrand
2025-07-25 11:08 ` Jann Horn
2025-07-25 11:12 ` David Hildenbrand
2025-07-25 11:24 ` Jann Horn
2025-07-25 11:31 ` David Hildenbrand [this message]
2025-07-25 11:32 ` Lorenzo Stoakes
2025-07-25 12:00 ` Jann Horn
2025-07-25 13:48 ` Lorenzo Stoakes
2025-07-25 14:10 ` Lorenzo Stoakes
2025-07-25 14:50 ` Jann Horn
2025-07-25 14:48 ` Jann Horn
2025-07-25 15:07 ` Lorenzo Stoakes
2025-07-25 15:15 ` Jann Horn
2025-07-25 15:22 ` Lorenzo Stoakes
2025-07-25 15:27 ` Jann Horn
2025-07-25 15:58 ` Lorenzo Stoakes
2025-07-25 15:05 ` Jann Horn
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=d6781e05-bde6-490c-af79-97993ed9018e@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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