From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-mm <linux-mm@kvack.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: next-20240826: arm: tinyconfig: mm/vma.h:184:26: error: 'USER_PGTABLES_CEILING' undeclared (first use in this function)
Date: Mon, 26 Aug 2024 14:13:05 +0100 [thread overview]
Message-ID: <5697d788-1206-421b-9c9a-3887c90e1c6d@lucifer.local> (raw)
In-Reply-To: <CA+G9fYuTLbZ+UiONYVQbtREuOZXc3oWP5=x-qqDhmFRmFfPtHA@mail.gmail.com>
On Mon, Aug 26, 2024 at 06:06:59PM GMT, Naresh Kamboju wrote:
> The arm tinyconfig and allnoconfig builds failed on today's Linux next-20240826
> due to following build warnings / errors.
This was resolved in the fixpatch sent in [0] which should hopefully go to
mm-unstable and thus -next soon.
[0]: https://lore.kernel.org/all/7d0ea994-f750-49c5-b392-ae7117369cf3@lucifer.local/
P.S. this message doesn't seem (at least yet) to have hit the linux-mm
mailing list, don't know why.
>
> first seen on next-20240826.
> Good: next-20240823
> BAD: next-20240826
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> build log:
> --------
>
> In file included from mm/internal.h:22,
> from mm/filemap.c:52:
> mm/vma.h: In function 'init_vma_munmap':
> mm/vma.h:184:26: error: 'USER_PGTABLES_CEILING' undeclared (first use
> in this function)
> 184 | vms->unmap_end = USER_PGTABLES_CEILING;
> | ^~~~~~~~~~~~~~~~~~~~~
> mm/vma.h:184:26: note: each undeclared identifier is reported only
> once for each function it appears in
> make[4]: *** [scripts/Makefile.build:244: mm/filemap.o] Error 1
> In file included from mm/internal.h:22,
> from mm/oom_kill.c:50:
> mm/vma.h: In function 'init_vma_munmap':
> mm/vma.h:184:26: error: 'USER_PGTABLES_CEILING' undeclared (first use
> in this function)
> 184 | vms->unmap_end = USER_PGTABLES_CEILING;
> | ^~~~~~~~~~~~~~~~~~~~~
>
> Build Log links,
> --------
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240826/testrun/24951924/suite/build/test/gcc-13-tinyconfig/log
>
> Build failed comparison:
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240826/testrun/24951940/suite/build/test/clang-18-tinyconfig/history/
>
> metadata:
> ----
> git describe: next-20240826
> git repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git sha: 1ca4237ad9ce29b0c66fe87862f1da54ac56a1e8
> kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2lC5HukjOlVYM52f7n4rm8EXOLG/config
> build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2lC5HukjOlVYM52f7n4rm8EXOLG/
> toolchain: clang-18 and gcc-13
> config: tinyconfig and allnoconfig
>
> Steps to reproduce:
> ---------
> - tuxmake --runtime podman --target-arch arm --toolchain gcc-13
> --kconfig tinyconfig
>
> --
> Linaro LKFT
> https://lkft.linaro.org
next prev parent reply other threads:[~2024-08-26 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:36 Naresh Kamboju
2024-08-26 13:13 ` Lorenzo Stoakes [this message]
2024-08-26 14:41 ` Liam R. Howlett
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=5697d788-1206-421b-9c9a-3887c90e1c6d@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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