All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jack-fs:bdev_handle 29/29] fs/cramfs/inode.c:498:17: error: implicit declaration of function 'blkdev_put'
Date: Sat, 12 Aug 2023 04:12:21 +0800	[thread overview]
Message-ID: <202308120445.mARUDRQa-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git bdev_handle
head:   1b96ba5f6b5fcb2bd0a267c592add81699cbf6c8
commit: 1b96ba5f6b5fcb2bd0a267c592add81699cbf6c8 [29/29] block: Remove blkdev_get_by_*() functions
config: xtensa-randconfig-r036-20230812 (https://download.01.org/0day-ci/archive/20230812/202308120445.mARUDRQa-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308120445.mARUDRQa-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/202308120445.mARUDRQa-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/cramfs/inode.c: In function 'cramfs_kill_sb':
>> fs/cramfs/inode.c:498:17: error: implicit declaration of function 'blkdev_put' [-Werror=implicit-function-declaration]
     498 |                 blkdev_put(sb->s_bdev, sb);
         |                 ^~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/blkdev_put +498 fs/cramfs/inode.c

eddcd97659e31f Nicolas Pitre     2017-10-12  484  
2309fb8ef40e82 Al Viro           2013-12-10  485  static void cramfs_kill_sb(struct super_block *sb)
^1da177e4c3f41 Linus Torvalds    2005-04-16  486  {
f7f4f4dd6948e3 Al Viro           2013-12-10  487  	struct cramfs_sb_info *sbi = CRAMFS_SB(sb);
31d92e55198d4e Fabian Frederick  2014-08-08  488  
a23edcb080c703 Jan Kara          2023-07-24  489  	generic_shutdown_super(sb);
a23edcb080c703 Jan Kara          2023-07-24  490  
08a8f308688032 Joe Perches       2018-05-13  491  	if (IS_ENABLED(CONFIG_CRAMFS_MTD) && sb->s_mtd) {
99c18ce580c6cc Nicolas Pitre     2017-10-13  492  		if (sbi && sbi->mtd_point_size)
99c18ce580c6cc Nicolas Pitre     2017-10-13  493  			mtd_unpoint(sb->s_mtd, 0, sbi->mtd_point_size);
a23edcb080c703 Jan Kara          2023-07-24  494  		put_mtd_device(sb->s_mtd);
a23edcb080c703 Jan Kara          2023-07-24  495  		sb->s_mtd = NULL;
99c18ce580c6cc Nicolas Pitre     2017-10-13  496  	} else if (IS_ENABLED(CONFIG_CRAMFS_BLOCKDEV) && sb->s_bdev) {
a23edcb080c703 Jan Kara          2023-07-24  497  		sync_blockdev(sb->s_bdev);
87b02a2ec40b29 Christoph Hellwig 2023-08-02 @498  		blkdev_put(sb->s_bdev, sb);
99c18ce580c6cc Nicolas Pitre     2017-10-13  499  	}
2309fb8ef40e82 Al Viro           2013-12-10  500  	kfree(sbi);
^1da177e4c3f41 Linus Torvalds    2005-04-16  501  }
^1da177e4c3f41 Linus Torvalds    2005-04-16  502  

:::::: The code at line 498 was first introduced by commit
:::::: 87b02a2ec40b2944ae4a2fdb078a53e39fca67a5 fs: use the super_block as holder when mounting file systems

:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Christian Brauner <brauner@kernel.org>

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

                 reply	other threads:[~2023-08-11 20:12 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=202308120445.mARUDRQa-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jack@suse.cz \
    --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 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.