All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Clark <robdclark@chromium.org>,
	llvm@lists.linux.dev
Subject: Re: Build failure in v5.15.133
Date: Fri, 29 Sep 2023 08:48:19 -0700	[thread overview]
Message-ID: <ZRbxw45Cc5wHXRXZ@google.com> (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.
> 
> Guenter

Thanks for the report, our CI is also pretty red for ARCH=arm64
linux-5.15.y builds. Also one ARCH=arm build we have that's using
Alpine's config is hitting the same issue.  Making note of this with our
ML CC'ed so that other folks don't potentially re-triage. Happy to hear
there's already a fix inbound.

      parent reply	other threads:[~2023-09-29 15:48 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
2023-09-29 15:48 ` Nick Desaulniers [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=ZRbxw45Cc5wHXRXZ@google.com \
    --to=ndesaulniers@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=llvm@lists.linux.dev \
    --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 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.