From: David Hildenbrand <david@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Gavin Guo <gavinguo@igalia.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
willy@infradead.org, ziy@nvidia.com, linmiaohe@huawei.com,
revest@google.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/huge_memory: fix dereferencing invalid pmd migration entry
Date: Thu, 17 Apr 2025 09:18:39 +0200 [thread overview]
Message-ID: <83f17b85-c9fa-43a0-bec1-22c8565b67ad@redhat.com> (raw)
In-Reply-To: <6787d0ea-a1b9-08cf-1f48-e361058eec20@google.com>
On 17.04.25 07:36, Hugh Dickins wrote:
> On Wed, 16 Apr 2025, David Hildenbrand wrote:
>>
>> Why not something like
>>
>> struct folio *entry_folio;
>>
>> if (folio) {
>> if (is_pmd_migration_entry(*pmd))
>> entry_folio = pfn_swap_entry_folio(pmd_to_swp_entry(*pmd)));
>> else
>> entry_folio = pmd_folio(*pmd));
>>
>> if (folio != entry_folio)
>> return;
>> }
>
> My own preference is to not add unnecessary code:
> if folio and pmd_migration entry, we're not interested in entry_folio.
> But yes it could be written in lots of other ways.
While I don't disagree about "not adding unnecessary code" in general,
in this particular case just looking the folio up properly might be the
better alternative to reasoning about locking rules with conditional
input parameters :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-17 7:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 7:27 Gavin Guo
2025-04-14 16:50 ` Zi Yan
2025-04-15 10:07 ` Gavin Guo
2025-04-15 15:57 ` Zi Yan
2025-04-17 5:29 ` Hugh Dickins
2025-04-18 13:25 ` Zi Yan
2025-04-17 5:03 ` Hugh Dickins
2025-04-16 16:10 ` David Hildenbrand
2025-04-17 5:36 ` Hugh Dickins
2025-04-17 7:18 ` David Hildenbrand [this message]
2025-04-17 8:07 ` David Hildenbrand
2025-04-17 8:09 ` David Hildenbrand
2025-04-17 8:55 ` Hugh Dickins
2025-04-17 9:04 ` David Hildenbrand
2025-04-17 11:21 ` Gavin Guo
2025-04-17 11:32 ` Zi Yan
2025-04-17 12:02 ` Gavin Guo
2025-04-17 12:10 ` Zi Yan
2025-04-17 12:38 ` Gavin Guo
2025-04-17 11:36 ` David Hildenbrand
2025-04-17 12:05 ` Gavin Guo
2025-04-17 4:38 ` Hugh Dickins
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=83f17b85-c9fa-43a0-bec1-22c8565b67ad@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gavinguo@igalia.com \
--cc=hughd@google.com \
--cc=kernel-dev@igalia.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=revest@google.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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