From: linke li <lilinke99@qq.com>
To: rientjes@google.com
Cc: 42.hyeyoo@gmail.com, akpm@linux-foundation.org, cl@linux.com,
iamjoonsoo.kim@lge.com, lilinke99@qq.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
penberg@kernel.org, roman.gushchin@linux.dev, vbabka@suse.cz,
xujianhao01@gmail.com
Subject: Re: [PATCH] mm/slub: mark racy access on slab->freelist
Date: Mon, 29 Apr 2024 10:25:15 +0800 [thread overview]
Message-ID: <tencent_7D666329DA16C3E9303F1DB5A06B0AB2A407@qq.com> (raw)
In-Reply-To: <1096134d-df6f-185d-240f-8a774d66f98f@google.com>
> Thanks! Do you have a data race report to copy+paste into the commit
> description so people can search for it if they stumble across the same
> thing?
I don't have a data race report, just try to analyze the code statically
and then check it manually. I hope I could help in some way.
next prev parent reply other threads:[~2024-04-29 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 8:51 [PATCH] mm/slub: mark racy access on slab->freelist linke li
2024-04-28 8:10 ` David Rientjes
2024-04-29 2:25 ` linke li [this message]
2024-05-02 12:23 ` Vlastimil Babka
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=tencent_7D666329DA16C3E9303F1DB5A06B0AB2A407@qq.com \
--to=lilinke99@qq.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=xujianhao01@gmail.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.