From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Chao Yu <chao@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] build failure of next-20220914 due to 64c11570d64d ("f2fs: fix to do sanity check on summary info")
Date: Wed, 14 Sep 2022 12:55:03 +0100 [thread overview]
Message-ID: <YyHBF99sC/vQdI3v@debian> (raw)
Hi All,
The builds of arm64 allmodconfig with clang have failed to build
next-20220914 with the error:
fs/f2fs/recovery.c:509:17: error: variable 'ino' is uninitialized when used here [-Werror,-Wuninitialized]
ofs_in_node, ino, nid, max_addrs);
^~~
fs/f2fs/f2fs.h:2376:35: note: expanded from macro 'f2fs_err'
f2fs_printk(sbi, KERN_ERR fmt, ##__VA_ARGS__)
^~~~~~~~~~~
fs/f2fs/recovery.c:475:11: note: initialize the variable 'ino' to silence this warning
nid_t ino, nid;
^
= 0
1 error generated.
git bisect pointed to 64c11570d64d ("f2fs: fix to do sanity check on summary info").
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Chao Yu <chao@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-next@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: build failure of next-20220914 due to 64c11570d64d ("f2fs: fix to do sanity check on summary info")
Date: Wed, 14 Sep 2022 12:55:03 +0100 [thread overview]
Message-ID: <YyHBF99sC/vQdI3v@debian> (raw)
Hi All,
The builds of arm64 allmodconfig with clang have failed to build
next-20220914 with the error:
fs/f2fs/recovery.c:509:17: error: variable 'ino' is uninitialized when used here [-Werror,-Wuninitialized]
ofs_in_node, ino, nid, max_addrs);
^~~
fs/f2fs/f2fs.h:2376:35: note: expanded from macro 'f2fs_err'
f2fs_printk(sbi, KERN_ERR fmt, ##__VA_ARGS__)
^~~~~~~~~~~
fs/f2fs/recovery.c:475:11: note: initialize the variable 'ino' to silence this warning
nid_t ino, nid;
^
= 0
1 error generated.
git bisect pointed to 64c11570d64d ("f2fs: fix to do sanity check on summary info").
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
next reply other threads:[~2022-09-14 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 11:55 Sudip Mukherjee (Codethink) [this message]
2022-09-14 11:55 ` build failure of next-20220914 due to 64c11570d64d ("f2fs: fix to do sanity check on summary info") Sudip Mukherjee (Codethink)
2022-09-14 12:00 ` [f2fs-dev] " Chao Yu
2022-09-14 12:00 ` Chao Yu
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=YyHBF99sC/vQdI3v@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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.