From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
clang-built-linux <llvm@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Lance Yang <ioworker0@gmail.com>
Subject: mm: huge_memory.c:2736:31: error: variable 'page' is uninitialized when used here [-Werror,-Wuninitialized]
Date: Wed, 26 Jun 2024 22:14:56 +0530 [thread overview]
Message-ID: <CA+G9fYv-rWNXZ9JxA19qSP0r+jhPDaMJejKbckN72kT1UpQ3QA@mail.gmail.com> (raw)
The x86_64 clang builds failed on Linux next due to these warnings / errors.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build error:
------
mm/huge_memory.c:2736:31: error: variable 'page' is uninitialized when
used here [-Werror,-Wuninitialized]
2736 | folio_remove_rmap_pmd(folio, page, vma);
| ^~~~
/builds/linux/mm/huge_memory.c:2700:19: note: initialize the variable
'page' to silence this warning
2700 | struct page *page;
| ^
| = NULL
1 error generated.
patch that is causing this build failures,
mm/vmscan: avoid split lazyfree THP during shrink_folio_list()
metadata:
--
git_describe: next-20240625
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: 0fc4bfab2cd4 ("Add linux-next specific files for 20240625")
arch: x86_64
toolchain: clang-18
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2iNfPlsMdxsqZTOC14r1xZZxq8X/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240625/testrun/24448204/suite/build/test/clang-18-lkftconfig/details/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-06-26 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 16:44 Naresh Kamboju [this message]
2024-06-26 17:00 ` Nathan Chancellor
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=CA+G9fYv-rWNXZ9JxA19qSP0r+jhPDaMJejKbckN72kT1UpQ3QA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@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