From: Sasha Levin <sashal@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Clark <robdclark@chromium.org>
Subject: Re: Build failure in v5.15.133
Date: Thu, 28 Sep 2023 07:04:55 -0400 [thread overview]
Message-ID: <ZRVd13RQgi5v3K4P@sashalap> (raw)
In-Reply-To: <e56ced8d-d09d-469b-80df-0cc2bdd943f4@roeck-us.net>
On Wed, Sep 27, 2023 at 06:37:10AM -0700, Guenter Roeck wrote:
>Hi,
>
>I see the following build failure with v5.15.133.
>
>Build reference: v5.15.133
>Compiler version: aarch64-linux-gcc (GCC) 11.4.0
>Assembler version: GNU assembler (GNU Binutils) 2.40
>
>Building arm64:allnoconfig ... passed
>Building arm64:tinyconfig ... passed
>Building arm64:defconfig ... failed
>--------------
>Error log:
>drivers/interconnect/core.c: In function 'icc_init':
>drivers/interconnect/core.c:1148:9: error: implicit declaration of function 'fs_reclaim_acquire' [-Werror=implicit-function-declaration]
> 1148 | fs_reclaim_acquire(GFP_KERNEL);
> | ^~~~~~~~~~~~~~~~~~
>drivers/interconnect/core.c:1150:9: error: implicit declaration of function 'fs_reclaim_release' [-Werror=implicit-function-declaration]
> 1150 | fs_reclaim_release(GFP_KERNEL);
> | ^~~~~~~~~~~~~~~~~~
>
>This also affects alpha:allmodconfig and m68k:allmodconfig. The problem
>was introduced with 'interconnect: Teach lockdep about icc_bw_lock order'.
>
>#include <linux/sched/mm.h> is missing. Presumably that is included
>indirectly in the upstream kernel, but I wasn't able to determine which
>commit added it.
Yeah, I added a fixup commit for the next release to address that issue,
thanks for the report!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-09-28 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 13:37 Build failure in v5.15.133 Guenter Roeck
2023-09-28 11:04 ` Sasha Levin [this message]
2023-09-29 15:48 ` Nick Desaulniers
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=ZRVd13RQgi5v3K4P@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=robdclark@chromium.org \
--cc=stable@vger.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