From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the cgroup tree
Date: Mon, 31 Oct 2022 07:52:53 -1000 [thread overview]
Message-ID: <Y2ALdT4e08bczeI+@slm.duckdns.org> (raw)
In-Reply-To: <20221031132331.76193df5@canb.auug.org.au>
On Mon, Oct 31, 2022 at 01:23:31PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the cgroup tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "css_tryget" [arch/x86/kvm/kvm-amd.ko] undefined!
> ERROR: modpost: "css_put" [arch/x86/kvm/kvm-amd.ko] undefined!
> ERROR: modpost: "css_put" [fs/btrfs/btrfs.ko] undefined!
> ERROR: modpost: "css_get" [fs/btrfs/btrfs.ko] undefined!
> ERROR: modpost: "css_put" [drivers/block/loop.ko] undefined!
> ERROR: modpost: "css_get" [drivers/block/loop.ko] undefined!
> ERROR: modpost: "css_put" [net/netfilter/xt_cgroup.ko] undefined!
>
> Caused by commit
>
> 6ab428604f72 ("cgroup: Implement DEBUG_CGROUP_REF")
>
> I have used the cgroup tree from next-20221028 for today.
Sorry about that. Fix patch added to the branch. Should be okay now.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-10-31 17:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 2:23 linux-next: build failure after merge of the cgroup tree Stephen Rothwell
2022-10-31 17:52 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 3:38 Stephen Rothwell
2023-12-07 4:18 ` Waiman Long
2023-07-17 1:34 Stephen Rothwell
2023-07-17 6:45 ` Miaohe Lin
2022-09-12 6:18 Stephen Rothwell
2022-09-12 7:38 ` Peter Zijlstra
2022-09-12 18:44 ` Tejun Heo
2022-09-12 22:16 ` Tejun Heo
2022-09-15 10:46 ` Peter Zijlstra
2022-10-10 20:57 ` Stephen Rothwell
2022-10-10 20:59 ` Tejun Heo
2022-08-29 3:29 Stephen Rothwell
2021-05-11 0:51 Stephen Rothwell
2021-05-11 1:10 ` Roman Gushchin
2021-05-11 1:31 ` Tejun Heo
2021-04-22 6:31 Stephen Rothwell
2015-09-25 3:26 Stephen Rothwell
2014-02-26 6:46 Stephen Rothwell
2014-02-26 13:44 ` Tejun Heo
2013-04-29 4:04 Stephen Rothwell
2013-04-29 22:55 ` Tejun Heo
2013-04-30 1:51 ` Benjamin Herrenschmidt
2012-09-14 3:17 Stephen Rothwell
2012-09-14 6:56 ` Daniel Wagner
2012-09-14 17:00 ` Tejun Heo
2012-09-14 18:32 ` Sedat Dilek
2012-09-14 18:34 ` Tejun Heo
2012-09-15 7:55 ` Sedat Dilek
2011-11-25 3:50 Stephen Rothwell
2011-11-27 19:33 ` Tejun Heo
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=Y2ALdT4e08bczeI+@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).