From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Vernon Yang <vernon2gm@gmail.com>
Cc: akpm@linux-foundation.org, ljs@kernel.org, nico.pache@linux.dev,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev, usama.arif@linux.dev, zokeefe@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org, Vernon Yang <yanglincheng@kylinos.cn>
Subject: Re: [PATCH v4 1/3] mm: khugepaged: fix swap entry value to folio_pfn()
Date: Tue, 8 Sep 2026 09:39:23 +0200 [thread overview]
Message-ID: <36658bb7-a753-4711-8659-5bca04a5949f@kernel.org> (raw)
In-Reply-To: <047c287f-bb00-4672-9ab8-3323cbae8f2e@gmail.com>
> > Yes, this is the approach Lorenzo[1] suggested in the previous version.
>
> [1] https://lore.kernel.org/linux-mm/ao6jVbVHLUmuY2UA@gremlin/
>
>> When result == SCAN_SUCCEED, failed_pfn == -1 no?
>
> Your understanding is completely correct, and I explained at the time
> that this was redundant.
>
Lorenzo said: "But it's not exactly a show stopper this :)", so I'd assume he'd
be fine with a single trace statement.
I'd say we keep it is simple as possible and use a single trace statement :)
--
Cheers,
David
next prev parent reply other threads:[~2026-09-08 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:59 [PATCH v4 0/3] mm: khugepaged: fix tracepoint UAF Vernon Yang
2026-08-28 5:59 ` [PATCH v4 1/3] mm: khugepaged: fix swap entry value to folio_pfn() Vernon Yang
2026-09-07 12:25 ` David Hildenbrand (Arm)
2026-09-08 1:35 ` Vernon Yang
2026-09-08 7:39 ` David Hildenbrand (Arm) [this message]
2026-08-28 5:59 ` [PATCH v4 2/3] mm: khugepaged: fix folio is used after pte_unmap_unlock() Vernon Yang
2026-09-07 12:26 ` David Hildenbrand (Arm)
2026-08-28 5:59 ` [PATCH v4 3/3] mm: khugepaged: fix folio is used after folio_put/unlock() Vernon Yang
2026-09-07 12:27 ` David Hildenbrand (Arm)
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=36658bb7-a753-4711-8659-5bca04a5949f@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=usama.arif@linux.dev \
--cc=vernon2gm@gmail.com \
--cc=yanglincheng@kylinos.cn \
--cc=zokeefe@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.