Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Namjae Jeon <linkinjeon@kernel.org>, Hyunchul Lee <hyc.lee@gmail.com>
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 ntfs tree
Date: Fri, 31 Jul 2026 14:50:13 +0100	[thread overview]
Message-ID: <amyoFfMXA9fI2hbF@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

Hi all,

After merging the ntfs tree, today's linux-next build (x86_64
allmodconfig) failed like this:

/tmp/next/build/fs/ntfs/attrlist.c:183:6: error: variable 'new_al' is used uninitialized whenever 'if' condition is true [-Werror,-Wsometimes-uninitialized]
  183 |         if (!NInoAttrList(ni) || !ni->attr_list) {
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/fs/ntfs/attrlist.c:317:6: note: uninitialized use occurs here
  317 |         if (new_al)
      |             ^~~~~~
/tmp/next/build/fs/ntfs/attrlist.c:183:2: note: remove the 'if' if its condition is always false
  183 |         if (!NInoAttrList(ni) || !ni->attr_list) {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  184 |                 err = -ENOENT;
      |                 ~~~~~~~~~~~~~~
  185 |                 goto err_out;
      |                 ~~~~~~~~~~~~~
  186 |         }
      |         ~
/tmp/next/build/fs/ntfs/attrlist.c:183:6: error: variable 'new_al' is used uninitialized whenever '||' condition is true [-Werror,-Wsometimes-uninitialized]
  183 |         if (!NInoAttrList(ni) || !ni->attr_list) {
      |             ^~~~~~~~~~~~~~~~~
/tmp/next/build/fs/ntfs/attrlist.c:317:6: note: uninitialized use occurs here
  317 |         if (new_al)
      |             ^~~~~~
/tmp/next/build/fs/ntfs/attrlist.c:183:6: note: remove the '||' if its condition is always false
  183 |         if (!NInoAttrList(ni) || !ni->attr_list) {
      |             ^~~~~~~~~~~~~~~~~~~~
/tmp/next/build/fs/ntfs/attrlist.c:149:12: note: initialize the variable 'new_al' to silence this warning
  149 |         u8 *new_al;
      |                   ^
      |                    = NULL
2 errors generated.

Caused by commit

  57ad655524e85 (ntfs: protect attribute-list buffer replacement with attr_list_persist_lock)

I have used the tree from next-20260730 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-07-31 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 13:50 Mark Brown [this message]
2026-07-31 13:57 ` linux-next: build failure after merge of the ntfs tree Namjae Jeon

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=amyoFfMXA9fI2hbF@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=hyc.lee@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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