mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: gaoxu <gaoxu2@honor.com>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
	"\"Michal Koutný\"" <mkoutny@suse.com>,
	"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"surenb@google.com" <surenb@google.com>,
	yipengxiang <yipengxiang@honor.com>
Subject: Re: [PATCH] cgroup: Fix compilation issue due to cgroup_mutex not being exported
Date: Thu, 17 Apr 2025 06:27:56 -1000	[thread overview]
Message-ID: <aAEsDKh79cBV4P3i@slm.duckdns.org> (raw)
In-Reply-To: <24763f5c8a13421fa6dc3672a57a7836@honor.com>

On Thu, Apr 17, 2025 at 07:30:00AM +0000, gaoxu wrote:
> When adding folio_memcg function call in the zram module for
> Android16-6.12, the following error occurs during compilation:
> ERROR: modpost: "cgroup_mutex" [../soc-repo/zram.ko] undefined!
> 
> This error is caused by the indirect call to lockdep_is_held(&cgroup_mutex)
> within folio_memcg. The export setting for cgroup_mutex is controlled by
> the CONFIG_PROVE_RCU macro. If CONFIG_LOCKDEP is enabled while
> CONFIG_PROVE_RCU is not, this compilation error will occur.
> 
> To resolve this issue, add a parallel macro CONFIG_LOCKDEP control to
> ensure cgroup_mutex is properly exported when needed.
> 
> Signed-off-by: gao xu <gaoxu2@honor.com>

Applied to cgroup/for-6.15-fixes.

Thanks.

-- 
tejun

      parent reply	other threads:[~2025-04-17 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  7:30 gaoxu
2025-04-17  9:18 ` Michal Koutný
2025-04-17 16:16 ` Kamalesh Babulal
2025-04-18  2:03   ` 回复: " gaoxu
2025-04-17 16:27 ` Tejun Heo [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=aAEsDKh79cBV4P3i@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=gaoxu2@honor.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=surenb@google.com \
    --cc=yipengxiang@honor.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®