All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v9 6/9] jbd2: fast commit recovery path
Date: Sat, 19 Sep 2020 19:27:31 +0800	[thread overview]
Message-ID: <202009191906.wDmV0OXF%lkp@intel.com> (raw)
In-Reply-To: <20200919005451.3899779-7-harshadshirwadkar@gmail.com>

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

Hi Harshad,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on ext4/dev]
[also build test WARNING on linus/master v5.9-rc5 next-20200918]
[cannot apply to tip/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Harshad-Shirwadkar/ext4-add-fast-commits-feature/20200919-085652
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
config: x86_64-randconfig-a006-20200917 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ed79827aea444e6995fb3d36abc2bfd36331773c)
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
        # 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:61: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.

# https://github.com/0day-ci/linux/commit/1edf68c36f8df0e684d1c2bd25d324d43da4d444
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Harshad-Shirwadkar/ext4-add-fast-commits-feature/20200919-085652
git checkout 1edf68c36f8df0e684d1c2bd25d324d43da4d444
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: 43605 bytes --]

  reply	other threads:[~2020-09-19 11:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  0:54 [PATCH v9 0/9] ext4: add fast commits feature Harshad Shirwadkar
2020-09-19  0:54 ` [PATCH v9 1/9] doc: update ext4 and journalling docs to include fast commit feature Harshad Shirwadkar
2020-09-22 17:50   ` Darrick J. Wong
2020-09-24  6:56     ` harshad shirwadkar
2020-10-09 18:28   ` Theodore Y. Ts'o
2020-10-13  0:27     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 2/9] ext4: add fast_commit feature and handling for extended mount options Harshad Shirwadkar
2020-10-09 17:58   ` Theodore Y. Ts'o
2020-10-13  0:27     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 3/9] ext4 / jbd2: add fast commit initialization Harshad Shirwadkar
2020-09-19 15:22   ` kernel test robot
2020-09-19 15:22     ` kernel test robot
2020-10-09 16:10   ` Ritesh Harjani
2020-10-13  0:28     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 4/9] jbd2: add fast commit machinery Harshad Shirwadkar
2020-10-09 16:16   ` Ritesh Harjani
2020-10-13  0:27     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 5/9] ext4: main fast-commit commit path Harshad Shirwadkar
2020-09-19  4:03   ` kernel test robot
2020-09-19  8:19   ` kernel test robot
2020-09-19  8:19     ` kernel test robot
2020-09-20  1:34   ` kernel test robot
2020-10-09 17:04   ` Ritesh Harjani
2020-10-13  0:25     ` harshad shirwadkar
2020-10-09 19:14   ` Theodore Y. Ts'o
2020-10-13  0:27     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 6/9] jbd2: fast commit recovery path Harshad Shirwadkar
2020-09-19 11:27   ` kernel test robot [this message]
2020-09-19  0:54 ` [PATCH v9 7/9] ext4: " Harshad Shirwadkar
2020-09-19 14:15   ` kernel test robot
2020-09-19 14:15     ` kernel test robot
2020-10-09 17:14   ` Ritesh Harjani
2020-10-13  0:27     ` harshad shirwadkar
2020-09-19  0:54 ` [PATCH v9 8/9] ext4: add a mount opt to forcefully turn fast commits on Harshad Shirwadkar
2020-09-19  0:54 ` [PATCH v9 9/9] ext4: add fast commit stats in procfs Harshad Shirwadkar

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=202009191906.wDmV0OXF%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.