mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: Zi Yan <ziy@nvidia.com>, Hui Zhu <hui.zhu@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Brendan Jackman <brendan.jackman@linux.dev>,
	Johannes Weiner <hannes@cmpxchg.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: teawater <zhuhui@kylinos.cn>
Subject: Re: [PATCH] mm/compaction: annotate data race for zone->free_area[order].nr_free
Date: Thu, 29 Oct 2026 11:39:46 +0530	[thread overview]
Message-ID: <106f7353-05d6-4585-a538-4c0e38e87829@arm.com> (raw)
In-Reply-To: <DMGIMSCNW6YL.1R45Z2AH6EBKE@nvidia.com>



On 28/10/26 7:16 pm, Zi Yan wrote:
> On Wed Oct 28, 2026 at 6:30 AM EDT, Dev Jain wrote:
>>
>>
>> On 28/10/26 2:37 pm, Hui Zhu wrote:
>>> From: teawater <zhuhui@kylinos.cn>
>>>
>>> KCSAN reports a data-race on nr_free which also exists on mainline:
>>>
>>>   BUG: KCSAN: data-race in fast_isolate_freepages+0x284/0x1550 mm/compaction.c:1589
>>>
>>>   race at unknown origin, with read to 0xffff9894ff3dcb60 of 8 bytes by task 179078 on cpu 12:
>>>    fast_isolate_freepages+0x284/0x1550 mm/compaction.c:1589
>>>    isolate_freepages+0x52/0x650 mm/compaction.c:1722
>>>    compaction_alloc_noprof+0x36e/0x3e0 mm/compaction.c:1850
>>>    compaction_alloc+0x21/0x30 mm/compaction.c:1880
>>>    migrate_folio_unmap+0x7f/0x820 mm/migrate.c:1177
>>>    migrate_pages_batch+0x37e/0x1200 mm/migrate.c:1762
>>>    migrate_pages_sync+0xce/0x560 mm/migrate.c:1928
>>>    migrate_pages+0x8c6/0xc20 mm/migrate.c:2037
>>>    compact_zone+0x539/0x10b0 mm/compaction.c:2660
>>>    compact_zone_order+0x1b8/0x230 mm/compaction.c:2795
>>>    try_to_compact_pages+0x20b/0x630 mm/compaction.c:2851
>>>    __alloc_pages_direct_compact+0x98/0x2b0 mm/page_alloc.c:3722
>>>    __alloc_pages_slowpath.constprop.0+0x452/0xdf0 mm/page_alloc.c:4401
>>>    __alloc_pages_noprof+0x28a/0x2d0 mm/page_alloc.c:4794
>>>    alloc_pages_mpol_noprof+0x1b1/0x470 mm/mempolicy.c:2270
>>>    alloc_pages_noprof+0x7a/0xe0 mm/mempolicy.c:2347
>>>    io_mem_alloc_compound io_uring/io_uring.c:2848 [inline]
>>>    io_pages_map+0xb9/0x330 io_uring/io_uring.c:2892
>>>    io_allocate_scq_urings+0x231/0x300 io_uring/io_uring.c:3933
>>>    io_uring_create+0x29c/0x9c0 io_uring/io_uring.c:4091
>>>    io_uring_setup+0xb6/0x100 io_uring/io_uring.c:4203
>>>    __do_sys_io_uring_setup io_uring/io_uring.c:4230 [inline]
>>>    __se_sys_io_uring_setup io_uring/io_uring.c:4224 [inline]
>>>    __x64_sys_io_uring_setup+0x66/0xe0 io_uring/io_uring.c:4224
>>>    x64_sys_call+0x1816/0x1d90 arch/x86/include/generated/asm/syscalls_64.h:426
>>>    do_syscall_x64 arch/x86/entry/common.c:51 [inline]
>>>    do_syscall_64+0x70/0x2a0 arch/x86/entry/common.c:81
>>>    entry_SYSCALL_64_after_hwframe+0x76/0xe0
>>>
>>>   value changed: 0x00000000000002f4 -> 0x00000000000002f5
>>>
>>> nr_free is only updated with zone->lock held, but fast_isolate_freepages()
>>> and fast_find_migrateblock() read it locklessly to skip an order that has
>>> no free pages.  page_alloc.o is excluded from KCSAN, so the writer is not
>>> instrumented and the report is of unknown origin.
>>>
>>> The race is benign: a stale zero only skips the order for this round, and
>>> a stale non-zero just finds an empty MIGRATE_MOVABLE freelist under the
>>> lock.  Annotate both reads with data_race(), following commit
>>> af1c31acc853 ("mm/vmstat: annotate data race for zone->free_area[order].nr_free").
>>>
>>> No functional change intended.
>>>
>>> Signed-off-by: teawater <zhuhui@kylinos.cn>
>>
>> teawater? What?
>>
>>
>>> ---
>>>  mm/compaction.c | 12 ++++++++++--
>>>  1 file changed, 10 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/mm/compaction.c b/mm/compaction.c
>>> index f1b2060eb2016..499ec7ceaa3ed 100644
>>> --- a/mm/compaction.c
>>> +++ b/mm/compaction.c
>>> @@ -1601,7 +1601,11 @@ static void fast_isolate_freepages(struct compact_control *cc)
>>>  		unsigned int order_scanned = 0;
>>>  		unsigned long high_pfn = 0;
>>>  
>>> -		if (!area->nr_free)
>>> +		/*
>>> +		 * Access to nr_free is lockless as it is only a hint; a stale
>>> +		 * value is harmless. Use data_race to avoid KCSAN warning.
>>> +		 */
>>
>> The comment is noise, the reason of using data_race() is a well-known fact.
> 
> IIRC, checkpatch.pl requires a comment for each data_race(). The
> comments need to stay until you send a patch to change checkpatch.pl.

Okay makes sense.


> 
>>
>> Apart from that, do we have the same problem with zone_watermark_ok? It also
>> uses area->nr_free without zone lock.
>>
>>> +		if (!data_race(area->nr_free))
>>>  			continue;
>>>  
>>>  		spin_lock_irqsave(&cc->zone->lock, flags);
>>> @@ -2031,7 +2035,11 @@ static unsigned long fast_find_migrateblock(struct compact_control *cc)
>>>  		unsigned long flags;
>>>  		struct page *freepage;
>>>  
>>> -		if (!area->nr_free)
>>> +		/*
>>> +		 * Access to nr_free is lockless as it is only a hint; a stale
>>> +		 * value is harmless. Use data_race to avoid KCSAN warning.
>>> +		 */
>>> +		if (!data_race(area->nr_free))
>>>  			continue;
>>>  
>>>  		spin_lock_irqsave(&cc->zone->lock, flags);
> 
> 
> 
> 


  reply	other threads:[~2026-10-29  6:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28  9:07 Hui Zhu
2026-10-28 10:30 ` Dev Jain
2026-10-28 13:46   ` Zi Yan
2026-10-29  6:09     ` Dev Jain [this message]
2026-10-29  6:19   ` Hui Zhu
2026-10-29  6:45 ` Dev Jain

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=106f7353-05d6-4585-a538-4c0e38e87829@arm.com \
    --to=dev.jain@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=brendan.jackman@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=hui.zhu@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=zhuhui@kylinos.cn \
    --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

all inboxes | Powered by JetHome®