linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Matthew Garrett <matthew.garrett@nebula.com>,
	Jeremy Kerr <jk@ozlabs.org>, Ard Biesheuvel <ardb@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Anisse Astier <an.astier@criteo.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH 1/1] efivarfs: fix statfs() on efivarfs
Date: Sun, 10 Sep 2023 06:30:12 +0800	[thread overview]
Message-ID: <202309100610.zLYrHmqr-lkp@intel.com> (raw)
In-Reply-To: <20230909180812.10904-1-heinrich.schuchardt@canonical.com>

Hi Heinrich,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.5 next-20230908]
[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/Heinrich-Schuchardt/efivarfs-fix-statfs-on-efivarfs/20230910-020949
base:   linus/master
patch link:    https://lore.kernel.org/r/20230909180812.10904-1-heinrich.schuchardt%40canonical.com
patch subject: [PATCH 1/1] efivarfs: fix statfs() on efivarfs
config: riscv-randconfig-r003-20230910 (https://download.01.org/0day-ci/archive/20230910/202309100610.zLYrHmqr-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230910/202309100610.zLYrHmqr-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/202309100610.zLYrHmqr-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/efivarfs/super.c:45:6: warning: variable 'remaining_space' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
           if (efi_rt_services_supported(EFI_RT_SUPPORTED_QUERY_VARIABLE_INFO)) {
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/efivarfs/super.c:60:6: note: uninitialized use occurs here
           if (remaining_space > efivar_reserved_space())
               ^~~~~~~~~~~~~~~
   fs/efivarfs/super.c:45:2: note: remove the 'if' if its condition is always true
           if (efi_rt_services_supported(EFI_RT_SUPPORTED_QUERY_VARIABLE_INFO)) {
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/efivarfs/super.c:32:36: note: initialize the variable 'remaining_space' to silence this warning
           u64 storage_space, remaining_space, max_variable_size;
                                             ^
                                              = 0
   1 warning generated.


vim +45 fs/efivarfs/super.c

    26	
    27	static int efivarfs_statfs(struct dentry *dentry, struct kstatfs *buf)
    28	{
    29		const u32 attr = EFI_VARIABLE_NON_VOLATILE |
    30				 EFI_VARIABLE_BOOTSERVICE_ACCESS |
    31				 EFI_VARIABLE_RUNTIME_ACCESS;
    32		u64 storage_space, remaining_space, max_variable_size;
    33		efi_status_t status;
    34	
    35		/*
    36		 * This is not a normal filesystem, so no point in pretending it has a block
    37		 * size; we declare f_bsize to 1, so that we can then report the exact value
    38		 * sent by EFI QueryVariableInfo in f_blocks and f_bfree
    39		 */
    40		buf->f_bsize	= 1;
    41		buf->f_namelen	= NAME_MAX;
    42		buf->f_type	= dentry->d_sb->s_magic;
    43	
    44		/* Some UEFI firmware does not implement QueryVariable() */
  > 45		if (efi_rt_services_supported(EFI_RT_SUPPORTED_QUERY_VARIABLE_INFO)) {
    46			status = efivar_query_variable_info(attr, &storage_space,
    47							    &remaining_space,
    48							    &max_variable_size);
    49			if (status == EFI_SUCCESS) {
    50				buf->f_blocks	= storage_space;
    51				buf->f_bfree	= remaining_space;
    52			}
    53		}
    54	
    55		/*
    56		 * In f_bavail we declare the free space that the kernel will allow writing
    57		 * when the storage_paranoia x86 quirk is active. To use more, users
    58		 * should boot the kernel with efi_no_storage_paranoia.
    59		 */
    60		if (remaining_space > efivar_reserved_space())
    61			buf->f_bavail = remaining_space - efivar_reserved_space();
    62		else
    63			buf->f_bavail = 0;
    64	
    65		return 0;
    66	}
    67	static const struct super_operations efivarfs_ops = {
    68		.statfs = efivarfs_statfs,
    69		.drop_inode = generic_delete_inode,
    70		.evict_inode = efivarfs_evict_inode,
    71	};
    72	

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

      reply	other threads:[~2023-09-09 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 18:08 [PATCH 1/1] efivarfs: fix statfs() on efivarfs Heinrich Schuchardt
2023-09-09 22:30 ` kernel test robot [this message]

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=202309100610.zLYrHmqr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=an.astier@criteo.com \
    --cc=ardb@kernel.org \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jk@ozlabs.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=matthew.garrett@nebula.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).