linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shivank Garg <shivankg@amd.com>
To: Dev Jain <dev.jain@arm.com>,
	akpm@linux-foundation.org, david@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Cc: ziy@nvidia.com, baolin.wang@linux.alibaba.com,
	lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	npache@redhat.com, ryan.roberts@arm.com, fengwei.yin@intel.com,
	bharata@amd.com,
	syzbot+2b99589e33edbe9475ca@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/khugepaged: Fix race with folio splitting in hpage_collapse_scan_file()
Date: Fri, 23 May 2025 13:20:55 +0530	[thread overview]
Message-ID: <231ebbc1-2110-4d82-b4e9-5a1b1220d9c4@amd.com> (raw)
In-Reply-To: <25cb53a2-f90e-4a70-9541-2aee51d71561@arm.com>



On 5/22/2025 3:37 PM, Dev Jain wrote:
> 
> On 22/05/25 3:04 pm, Shivank Garg wrote:
>> folio_mapcount() checks folio_test_large() before proceeding to
> 
> 
> It is not very clear in the description, where is this folio_mapcount() call present?
> 
> Are you talking about is_refcount_suitable()?

Yes, The issue originates from is_refcount_suitable(), which internally relies on folio_mapcount(), which contain the race.

I'll update the description to make it clearer.

Thanks,
Shivank


      reply	other threads:[~2025-05-23  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  9:34 Shivank Garg
2025-05-22 10:01 ` Baolin Wang
2025-05-22 10:04   ` Dev Jain
2025-05-22 11:59   ` David Hildenbrand
2025-05-23  7:50     ` Shivank Garg
2025-05-22 10:02 ` Dev Jain
2025-05-22 10:07 ` Dev Jain
2025-05-23  7:50   ` Shivank Garg [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=231ebbc1-2110-4d82-b4e9-5a1b1220d9c4@amd.com \
    --to=shivankg@amd.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bharata@amd.com \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=syzbot+2b99589e33edbe9475ca@syzkaller.appspotmail.com \
    --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