public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org,
	Luis Chamberlain <mcgrof@kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Bart Van Assche <bvanassche@acm.org>
Subject: [mcgrof-next:20220707-dm-zoned-npo2 1/13] fs/btrfs/zoned.h:311:5: error: call to undeclared function 'bdev_zone_sectors'; ISO C99 and later do not support implicit function declarations
Date: Sat, 9 Jul 2022 11:17:04 +0800	[thread overview]
Message-ID: <202207091156.CM7phKD9-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git 20220707-dm-zoned-npo2
head:   3d1b6e41f76394610669e380da4f65bc5e7cf8ac
commit: a37ed4b355c02ec383a85c961f0e121df104cc1a [1/13] block: make bdev_nr_zones and disk_zone_no generic for npo2 zsze
config: hexagon-randconfig-r041-20220707 (https://download.01.org/0day-ci/archive/20220709/202207091156.CM7phKD9-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 77a38f6839980bfac61babb40d83772c51427011)
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
        # https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/commit/?id=a37ed4b355c02ec383a85c961f0e121df104cc1a
        git remote add mcgrof-next https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git
        git fetch --no-tags mcgrof-next 20220707-dm-zoned-npo2
        git checkout a37ed4b355c02ec383a85c961f0e121df104cc1a
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash block/ fs/btrfs/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from fs/btrfs/extent_io.c:30:
>> fs/btrfs/zoned.h:311:5: error: call to undeclared function 'bdev_zone_sectors'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                           (bdev_zone_sectors(bdev) << SECTOR_SHIFT);
                            ^
   fs/btrfs/zoned.h:311:5: note: did you mean 'bdev_nr_sectors'?
   include/linux/blkdev.h:807:24: note: 'bdev_nr_sectors' declared here
   static inline sector_t bdev_nr_sectors(struct block_device *bdev)
                          ^
   1 error generated.
--
>> block/ioctl.c:496:25: error: call to undeclared function 'bdev_zone_sectors'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                   return put_uint(argp, bdev_zone_sectors(bdev));
                                         ^
   block/ioctl.c:496:25: note: did you mean 'bdev_nr_sectors'?
   include/linux/blkdev.h:807:24: note: 'bdev_nr_sectors' declared here
   static inline sector_t bdev_nr_sectors(struct block_device *bdev)
                          ^
   1 error generated.


vim +/bdev_zone_sectors +311 fs/btrfs/zoned.h

5b316468983dfa9 Naohiro Aota       2020-11-10  298  
b70f509774ad4b7 Naohiro Aota       2020-11-10  299  static inline bool btrfs_check_device_zone_type(const struct btrfs_fs_info *fs_info,
b70f509774ad4b7 Naohiro Aota       2020-11-10  300  						struct block_device *bdev)
b70f509774ad4b7 Naohiro Aota       2020-11-10  301  {
b70f509774ad4b7 Naohiro Aota       2020-11-10  302  	if (btrfs_is_zoned(fs_info)) {
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  303  		/*
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  304  		 * We can allow a regular device on a zoned filesystem, because
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  305  		 * we will emulate the zoned capabilities.
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  306  		 */
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  307  		if (!bdev_is_zoned(bdev))
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  308  			return true;
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  309  
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04  310  		return fs_info->zone_size ==
3c9daa09ccd43f6 Johannes Thumshirn 2021-02-04 @311  			(bdev_zone_sectors(bdev) << SECTOR_SHIFT);
b70f509774ad4b7 Naohiro Aota       2020-11-10  312  	}
b70f509774ad4b7 Naohiro Aota       2020-11-10  313  
b70f509774ad4b7 Naohiro Aota       2020-11-10  314  	/* Do not allow Host Manged zoned device */
b70f509774ad4b7 Naohiro Aota       2020-11-10  315  	return bdev_zoned_model(bdev) != BLK_ZONED_HM;
b70f509774ad4b7 Naohiro Aota       2020-11-10  316  }
b70f509774ad4b7 Naohiro Aota       2020-11-10  317  

:::::: The code at line 311 was first introduced by commit
:::::: 3c9daa09ccd43f68104634020b364d834c01738c btrfs: zoned: allow zoned filesystems on non-zoned block devices

:::::: TO: Johannes Thumshirn <johannes.thumshirn@wdc.com>
:::::: CC: David Sterba <dsterba@suse.com>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-09  3:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202207091156.CM7phKD9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.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