Linux Documentation
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hongbo Li <lihongbo22@huawei.com>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	tytso@mit.edu, adilger.kernel@dilger.ca
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	lczerner@redhat.com, cmaiolino@redhat.com,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
	yi.zhang@huawei.com, lihongbo22@huawei.com
Subject: Re: [PATCH 1/4] fs: add blockdev parser for filesystem mount option.
Date: Mon, 27 May 2024 11:22:38 +0800	[thread overview]
Message-ID: <202405271100.aGNNnrKK-lkp@intel.com> (raw)
In-Reply-To: <20240527014717.690140-2-lihongbo22@huawei.com>

Hi Hongbo,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tytso-ext4/dev]
[also build test WARNING on brauner-vfs/vfs.all linus/master v6.10-rc1 next-20240523]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Hongbo-Li/fs-add-blockdev-parser-for-filesystem-mount-option/20240527-094930
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
patch link:    https://lore.kernel.org/r/20240527014717.690140-2-lihongbo22%40huawei.com
patch subject: [PATCH 1/4] fs: add blockdev parser for filesystem mount option.
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20240527/202405271100.aGNNnrKK-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240527/202405271100.aGNNnrKK-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405271100.aGNNnrKK-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/fs_parser.c:324:8: warning: variable 'f' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/fs_parser.c:343:29: note: uninitialized use occurs here
     343 |         ret = filename_lookup(dfd, f, LOOKUP_FOLLOW, &path, NULL);
         |                                    ^
   fs/fs_parser.c:324:4: note: remove the 'if' if its condition is always true
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     325 |                                 return 0;
   fs/fs_parser.c:316:20: note: initialize the variable 'f' to silence this warning
     316 |         struct filename *f;
         |                           ^
         |                            = NULL
>> fs/fs_parser.c:324:8: warning: variable 'put_f' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/fs_parser.c:360:6: note: uninitialized use occurs here
     360 |         if (put_f)
         |             ^~~~~
   fs/fs_parser.c:324:4: note: remove the 'if' if its condition is always true
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     325 |                                 return 0;
   fs/fs_parser.c:319:12: note: initialize the variable 'put_f' to silence this warning
     319 |         bool put_f;
         |                   ^
         |                    = 0
>> fs/fs_parser.c:324:8: warning: variable 'dfd' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/fs_parser.c:343:24: note: uninitialized use occurs here
     343 |         ret = filename_lookup(dfd, f, LOOKUP_FOLLOW, &path, NULL);
         |                               ^~~
   fs/fs_parser.c:324:4: note: remove the 'if' if its condition is always true
     324 |                         if (p->flags & fs_param_can_be_empty)
         |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     325 |                                 return 0;
   fs/fs_parser.c:315:9: note: initialize the variable 'dfd' to silence this warning
     315 |         int dfd;
         |                ^
         |                 = 0
   3 warnings generated.


vim +324 fs/fs_parser.c

   310	
   311	int fs_param_is_blockdev(struct p_log *log, const struct fs_parameter_spec *p,
   312			  struct fs_parameter *param, struct fs_parse_result *result)
   313	{
   314		int ret;
   315		int dfd;
   316		struct filename *f;
   317		struct inode *dev_inode;
   318		struct path path;
   319		bool put_f;
   320	
   321		switch (param->type) {
   322		case fs_value_is_string:
   323			if (!*param->string) {
 > 324				if (p->flags & fs_param_can_be_empty)
   325					return 0;
   326				break;
   327			}
   328			f = getname_kernel(param->string);
   329			if (IS_ERR(f))
   330				return fs_param_bad_value(log, param);
   331			dfd = AT_FDCWD;
   332			put_f = true;
   333			break;
   334		case fs_value_is_filename:
   335			f = param->name;
   336			dfd = param->dirfd;
   337			put_f = false;
   338			break;
   339		default:
   340			return fs_param_bad_value(log, param);
   341		}
   342	
   343		ret = filename_lookup(dfd, f, LOOKUP_FOLLOW, &path, NULL);
   344		if (ret < 0) {
   345			error_plog(log, "%s: Lookup failure for '%s'", param->key, f->name);
   346			goto out_putname;
   347		}
   348	
   349		dev_inode = d_backing_inode(path.dentry);
   350		if (!S_ISBLK(dev_inode->i_mode)) {
   351			error_plog(log, "%s: Non-blockdev passed as '%s'", param->key, f->name);
   352			ret = -1;
   353			goto out_putpath;
   354		}
   355		result->uint_32 = new_encode_dev(dev_inode->i_rdev);
   356	
   357	out_putpath:
   358		path_put(&path);
   359	out_putname:
   360		if (put_f)
   361			putname(f);
   362	
   363		return (ret < 0) ? fs_param_bad_value(log, param) : 0;
   364	}
   365	EXPORT_SYMBOL(fs_param_is_blockdev);
   366	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-05-27  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  1:47 [PATCH 0/4] enhance the path resolution capability in fs_parser Hongbo Li
2024-05-27  1:47 ` [PATCH 1/4] fs: add blockdev parser for filesystem mount option Hongbo Li
2024-05-27  3:22   ` kernel test robot [this message]
2024-05-27  1:47 ` [PATCH 2/4] fs: add path " Hongbo Li
2024-05-27  1:47 ` [PATCH 3/4] fs: ext4: support relative path for `journal_path` in " Hongbo Li
2024-05-27  1:47 ` [PATCH 4/4] fs: remove fs_lookup_param and its description Hongbo Li

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=202405271100.aGNNnrKK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=brauner@kernel.org \
    --cc=cmaiolino@redhat.com \
    --cc=jack@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=lihongbo22@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yi.zhang@huawei.com \
    /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