From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Lance Yang <lance.yang@linux.dev>
Cc: vernon2gm@gmail.com, akpm@linux-foundation.org, david@kernel.org,
ljs@kernel.org, nico.pache@linux.dev, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, usama.arif@linux.dev,
zokeefe@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 0/3] mm: khugepaged: fix tracepoint UAF
Date: Mon, 17 Aug 2026 15:24:52 +0800 [thread overview]
Message-ID: <bf0063c7-8db1-4e35-a785-d9a0dea9b2bb@linux.alibaba.com> (raw)
In-Reply-To: <811a8454-daef-4a2c-a1a8-4374e83f8c35@linux.dev>
On 8/17/26 10:53 AM, Lance Yang wrote:
>
>
> On 2026/8/17 10:25, Baolin Wang wrote:
>> Hi Lance,
>>
>> On 8/16/26 2:16 AM, Lance Yang wrote:
>>> +Cc Baolin
>>>
>>> On Sun, Aug 16, 2026 at 01:44:44AM +0800, Lance Yang wrote:
>>>>
>>>> On Sat, Aug 15, 2026 at 01:19:21PM +0800, Vernon Yang wrote:
> [...]
>> Otherwise, I can fix it. Thanks for your report and analysis.
>
> Yeah, please go ahead :) Thanks, Baolin!
FYI: I've posted the fix and verified it resolves the issue from my testing.
https://lore.kernel.org/all/ed34ca03ae7d65e89467fb87bc961f5497049c00.1786948410.git.baolin.wang@linux.alibaba.com/
prev parent reply other threads:[~2026-08-17 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 5:19 [PATCH v2 0/3] mm: khugepaged: fix tracepoint UAF Vernon Yang
2026-08-15 5:19 ` [PATCH v2 1/3] mm: khugepaged: fix swap entry value to folio_pfn() Vernon Yang
2026-08-15 5:19 ` [PATCH v2 2/3] mm: khugepaged: fix folio is used after pte_unmap_unlock() Vernon Yang
2026-08-15 5:19 ` [PATCH v2 3/3] mm: khugepaged: fix folio is used after folio_put/unlock() Vernon Yang
2026-08-15 17:44 ` [PATCH v2 0/3] mm: khugepaged: fix tracepoint UAF Lance Yang
2026-08-15 18:16 ` Lance Yang
2026-08-17 2:25 ` Baolin Wang
2026-08-17 2:53 ` Lance Yang
2026-08-17 7:24 ` Baolin Wang [this message]
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=bf0063c7-8db1-4e35-a785-d9a0dea9b2bb@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--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=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=vernon2gm@gmail.com \
--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.