linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	Muchun Song <songmuchun@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Vlastimil Babka <vbabka@kernel.org>,
	cgroups@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] mm: kmem: add lockdep assertion to obj_cgroup_memcg
Date: Wed, 31 Jul 2024 14:53:34 +0800	[thread overview]
Message-ID: <305D2228-2BE5-407B-95C3-FE4C9FD59826@linux.dev> (raw)
In-Reply-To: <20240730131822.a170e6da169da396a833aa4f@linux-foundation.org>



> On Jul 31, 2024, at 04:18, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> On Tue, 30 Jul 2024 20:52:04 +0200 Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> 
>> This patch landed in today's linux-next as commit 230b2f1f31b9 ("mm: 
>> kmem: add lockdep assertion to obj_cgroup_memcg"). I my tests I found 
>> that it triggers the following warning on Debian bookworm/sid system 
>> image running under QEMU RISCV64:
> 
> Thanks.  I'll drop the patch while this gets sorted out, to be nice to
> linux-next users.

Hi Andrew,

Please pick up this patch first [1], it is a fix for the above issue.

[1] https://lore.kernel.org/all/20240718083607.42068-1-songmuchun@bytedance.com/

Thanks.

  reply	other threads:[~2024-07-31  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  9:43 Muchun Song
2024-07-25 15:58 ` Shakeel Butt
2024-07-25 17:39 ` Roman Gushchin
2024-07-26  8:09 ` Vlastimil Babka (SUSE)
     [not found] ` <CGME20240730185206eucas1p28b14a1d9802ce2703bd13edc75e1b55d@eucas1p2.samsung.com>
2024-07-30 18:52   ` Marek Szyprowski
2024-07-30 20:18     ` Andrew Morton
2024-07-31  6:53       ` Muchun Song [this message]
2024-07-31  7:02     ` Muchun Song
2024-07-31  8:09       ` Marek Szyprowski

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=305D2228-2BE5-407B-95C3-FE4C9FD59826@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mhocko@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=songmuchun@bytedance.com \
    --cc=vbabka@kernel.org \
    /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