From: kernel test robot <lkp@intel.com>
To: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: [ext4:dev 10/44] fs/jbd2/recovery.c:258:6: warning: variable 'seq' is uninitialized when used here
Date: Fri, 9 Oct 2020 17:10:40 +0800 [thread overview]
Message-ID: <202010091737.hajyydHD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3295 bytes --]
Hi Harshad,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
head: ab7b179af3f98772f2433ddc4ace6b7924a4e862
commit: 23386fc5c4ce13c9be9a185e20f78dab355b17df [10/44] jbd2: fast commit recovery path
config: x86_64-randconfig-a004-20201009 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 4cfc4025cc1433ca5ef1c526053fc9c4bfe64109)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=23386fc5c4ce13c9be9a185e20f78dab355b17df
git remote add ext4 https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
git fetch --no-tags ext4 dev
git checkout 23386fc5c4ce13c9be9a185e20f78dab355b17df
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/jbd2/recovery.c:258:6: warning: variable 'seq' is uninitialized when used here [-Wuninitialized]
seq);
^~~
include/linux/jbd2.h:62:59: note: expanded from macro 'jbd_debug'
__jbd2_debug((n), __FILE__, __func__, __LINE__, (fmt), ##a)
^
fs/jbd2/recovery.c:241:18: note: initialize the variable 'seq' to silence this warning
unsigned int seq;
^
= 0
1 warning generated.
vim +/seq +258 fs/jbd2/recovery.c
234
235 static int fc_do_one_pass(journal_t *journal,
236 struct recovery_info *info, enum passtype pass)
237 {
238 unsigned int expected_commit_id = info->end_transaction;
239 unsigned long next_fc_block;
240 struct buffer_head *bh;
241 unsigned int seq;
242 int err = 0;
243
244 next_fc_block = journal->j_first_fc;
245 if (!journal->j_fc_replay_callback)
246 return 0;
247
248 while (next_fc_block <= journal->j_last_fc) {
249 jbd_debug(3, "Fast commit replay: next block %ld",
250 next_fc_block);
251 err = jread(&bh, journal, next_fc_block);
252 if (err) {
253 jbd_debug(3, "Fast commit replay: read error");
254 break;
255 }
256
257 jbd_debug(3, "Processing fast commit blk with seq %d",
> 258 seq);
259 err = journal->j_fc_replay_callback(journal, bh, pass,
260 next_fc_block - journal->j_first_fc,
261 expected_commit_id);
262 next_fc_block++;
263 if (err < 0 || err == JBD2_FC_REPLAY_STOP)
264 break;
265 err = 0;
266 }
267
268 if (err)
269 jbd_debug(3, "Fast commit replay failed, err = %d\n", err);
270
271 return err;
272 }
273
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35031 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ext4:dev 10/44] fs/jbd2/recovery.c:258:6: warning: variable 'seq' is uninitialized when used here
Date: Fri, 09 Oct 2020 17:10:40 +0800 [thread overview]
Message-ID: <202010091737.hajyydHD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3379 bytes --]
Hi Harshad,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
head: ab7b179af3f98772f2433ddc4ace6b7924a4e862
commit: 23386fc5c4ce13c9be9a185e20f78dab355b17df [10/44] jbd2: fast commit recovery path
config: x86_64-randconfig-a004-20201009 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 4cfc4025cc1433ca5ef1c526053fc9c4bfe64109)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=23386fc5c4ce13c9be9a185e20f78dab355b17df
git remote add ext4 https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
git fetch --no-tags ext4 dev
git checkout 23386fc5c4ce13c9be9a185e20f78dab355b17df
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/jbd2/recovery.c:258:6: warning: variable 'seq' is uninitialized when used here [-Wuninitialized]
seq);
^~~
include/linux/jbd2.h:62:59: note: expanded from macro 'jbd_debug'
__jbd2_debug((n), __FILE__, __func__, __LINE__, (fmt), ##a)
^
fs/jbd2/recovery.c:241:18: note: initialize the variable 'seq' to silence this warning
unsigned int seq;
^
= 0
1 warning generated.
vim +/seq +258 fs/jbd2/recovery.c
234
235 static int fc_do_one_pass(journal_t *journal,
236 struct recovery_info *info, enum passtype pass)
237 {
238 unsigned int expected_commit_id = info->end_transaction;
239 unsigned long next_fc_block;
240 struct buffer_head *bh;
241 unsigned int seq;
242 int err = 0;
243
244 next_fc_block = journal->j_first_fc;
245 if (!journal->j_fc_replay_callback)
246 return 0;
247
248 while (next_fc_block <= journal->j_last_fc) {
249 jbd_debug(3, "Fast commit replay: next block %ld",
250 next_fc_block);
251 err = jread(&bh, journal, next_fc_block);
252 if (err) {
253 jbd_debug(3, "Fast commit replay: read error");
254 break;
255 }
256
257 jbd_debug(3, "Processing fast commit blk with seq %d",
> 258 seq);
259 err = journal->j_fc_replay_callback(journal, bh, pass,
260 next_fc_block - journal->j_first_fc,
261 expected_commit_id);
262 next_fc_block++;
263 if (err < 0 || err == JBD2_FC_REPLAY_STOP)
264 break;
265 err = 0;
266 }
267
268 if (err)
269 jbd_debug(3, "Fast commit replay failed, err = %d\n", err);
270
271 return err;
272 }
273
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35031 bytes --]
next reply other threads:[~2020-10-09 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 9:10 kernel test robot [this message]
2020-10-09 9:10 ` [ext4:dev 10/44] fs/jbd2/recovery.c:258:6: warning: variable 'seq' is uninitialized when used here kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2020-10-09 8:15 kernel test robot
2020-10-09 8:15 ` kernel test robot
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=202010091737.hajyydHD-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=harshadshirwadkar@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.