The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Vernon Yang <vernon2gm@gmail.com>,
	akpm@linux-foundation.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 v3 3/3] mm: khugepaged: fix folio is used after folio_put/unlock()
Date: Wed, 26 Aug 2026 09:23:13 +0100	[thread overview]
Message-ID: <ao6hClAw33UnGmET@gremlin> (raw)
In-Reply-To: <77412338-b54c-455b-84da-1f39db641c90@kernel.org>

On Wed, Aug 26, 2026 at 10:14:43AM +0200, David Hildenbrand (Arm) wrote:
> Note that the monstrosity we called pfn_t no longer exits. :)

Oops! :) Fair enough. I mistook it for one of the various benign typedef
unsigned long xxx_t decls and forgot (repressed?) the horror show elements of
struct { ... } with flags and what not.

Vernon - please disregard the pfn_t feedback, obviously :)

>
> --
> Cheers,
>
> David

--
Cheers, Lorenzo

  reply	other threads:[~2026-08-26  8:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  9:29 [PATCH v3 0/3] mm: khugepaged: fix tracepoint UAF Vernon Yang
2026-08-24  9:29 ` [PATCH v3 1/3] mm: khugepaged: fix swap entry value to folio_pfn() Vernon Yang
2026-08-24 11:54   ` David Hildenbrand (Arm)
2026-08-26  2:44     ` Vernon Yang
2026-08-26  7:57       ` David Hildenbrand (Arm)
2026-08-26  8:07         ` Lorenzo Stoakes (ARM)
2026-08-26  8:08           ` David Hildenbrand (Arm)
2026-08-26  8:11             ` Lorenzo Stoakes (ARM)
2026-08-26  8:16               ` David Hildenbrand (Arm)
2026-08-26  8:24                 ` David Hildenbrand (Arm)
2026-08-26  8:35                   ` Lorenzo Stoakes (ARM)
2026-08-26  9:10                     ` David Hildenbrand (Arm)
2026-08-26  9:21                     ` Vernon Yang
2026-08-26 11:04                       ` Lorenzo Stoakes (ARM)
2026-08-26  9:08         ` Vernon Yang
2026-08-24  9:29 ` [PATCH v3 2/3] mm: khugepaged: fix folio is used after pte_unmap_unlock() Vernon Yang
2026-08-24 11:57   ` David Hildenbrand (Arm)
2026-08-26  2:46     ` Vernon Yang
2026-08-26  7:58       ` David Hildenbrand (Arm)
2026-08-26  8:12   ` Lorenzo Stoakes (ARM)
2026-08-26  8:42     ` Lorenzo Stoakes (ARM)
2026-08-24  9:29 ` [PATCH v3 3/3] mm: khugepaged: fix folio is used after folio_put/unlock() Vernon Yang
2026-08-24 11:59   ` David Hildenbrand (Arm)
2026-08-26  2:47     ` Vernon Yang
2026-08-26  8:09   ` Lorenzo Stoakes (ARM)
2026-08-26  8:14     ` David Hildenbrand (Arm)
2026-08-26  8:23       ` Lorenzo Stoakes (ARM) [this message]
2026-08-26  8:41     ` Lorenzo Stoakes (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=ao6hClAw33UnGmET@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox