From: Mark Brown <broonie@kernel•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the mm-unstable tree
Date: Wed, 3 Jun 2026 10:39:14 +0100 [thread overview]
Message-ID: <ah_2QuKro4gYRP1c@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
Hi all,
After merging the mm-unstable tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/tmp/next/build/mm/khugepaged.c:1357:6: error: variable 'pte' is used uninitialized whenever 'if' condition is true
[-Werror,-Wsometimes-uninitialized]
1357 | if (result != SCAN_SUCCEED)
| ^~~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/mm/khugepaged.c:1458:6: note: uninitialized use occurs here
1458 | if (pte)
| ^~~
/tmp/next/build/mm/khugepaged.c:1357:2: note: remove the 'if' if its condition is always false
1357 | if (result != SCAN_SUCCEED)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
1358 | goto out_up_write;
| ~~~~~~~~~~~~~~~~~
/tmp/next/build/mm/khugepaged.c:1352:6: error: variable 'pte' is used uninitialized whenever 'if' condition is true
[-Werror,-Wsometimes-uninitialized]
1352 | if (result != SCAN_SUCCEED)
| ^~~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/mm/khugepaged.c:1458:6: note: uninitialized use occurs here
1458 | if (pte)
| ^~~
/tmp/next/build/mm/khugepaged.c:1352:2: note: remove the 'if' if its condition is always false
1352 | if (result != SCAN_SUCCEED)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
1353 | goto out_up_write;
| ~~~~~~~~~~~~~~~~~
/tmp/next/build/mm/khugepaged.c:1296:12: note: initialize the variable 'pte' to silence this warning
1296 | pte_t *pte;
| ^
| = NULL
2 errors generated.
Caused by this diff:
diff --git a/mm/khugepaged.c b/mm/khugepaged.c
index 8ffb47f1e8453..2837f12618583 100644
--- a/mm/khugepaged.c
+++ b/mm/khugepaged.c
@@ -1293,7 +1293,7 @@ static enum scan_result collapse_huge_page(struct mm_struct *mm, unsigned long s
const unsigned long end_addr = start_addr + (PAGE_SIZE << order);
LIST_HEAD(compound_pagelist);
pmd_t *pmd, _pmd;
- pte_t *pte = NULL;
+ pte_t *pte;
pgtable_t pgtable;
struct folio *folio;
spinlock_t *pmd_ptl, *pte_ptl;
which git annotate is getting very confused about the source of unless
it's a dropped commit. I have reverted that hunk.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-06-03 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 9:39 Mark Brown [this message]
2026-06-03 18:17 ` linux-next: build failure after merge of the mm-unstable tree Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2026-03-18 13:51 Mark Brown
2026-03-18 18:20 ` Andrew Morton
2026-03-18 19:08 ` Mark Brown
2026-01-07 0:16 Stephen Rothwell
2025-09-11 6:05 Stephen Rothwell
2025-09-11 7:44 ` Kairui Song
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=ah_2QuKro4gYRP1c@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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