From: kernel test robot <lkp@intel.com>
To: mwilck@suse.com,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
James Bottomley <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
Hannes Reinecke <hare@suse.de>, Martin Wilck <mwilck@suse.com>,
Karan Tilak Kumar <kartilak@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>
Subject: Re: [PATCH v6 6/7] scsi: replace scsi_target_block() by scsi_block_targets()
Date: Wed, 14 Jun 2023 05:16:04 +0800 [thread overview]
Message-ID: <202306140503.hMWyg8Xa-lkp@intel.com> (raw)
In-Reply-To: <20230613174227.11235-7-mwilck@suse.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on mkp-scsi/for-next]
[also build test ERROR on jejb-scsi/for-next axboe-block/for-next linus/master v6.4-rc6 next-20230613]
[cannot apply to hch-configfs/for-next]
[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/mwilck-suse-com/bsg-increase-number-of-devices/20230614-014437
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/r/20230613174227.11235-7-mwilck%40suse.com
patch subject: [PATCH v6 6/7] scsi: replace scsi_target_block() by scsi_block_targets()
config: arm-randconfig-r011-20230612 (https://download.01.org/0day-ci/archive/20230614/202306140503.hMWyg8Xa-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
git remote add mkp-scsi https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
git fetch mkp-scsi for-next
git checkout mkp-scsi/for-next
b4 shazam https://lore.kernel.org/r/20230613174227.11235-7-mwilck@suse.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/scsi/
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/202306140503.hMWyg8Xa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/scsi/scsi_lib.c:2912:1: error: conflicting types for 'scsi_block_targets'
2912 | scsi_block_targets(struct device *dev, struct Scsi_Host *shost)
| ^
include/scsi/scsi_device.h:459:6: note: previous declaration is here
459 | void scsi_block_targets(struct Scsi_Host *shost, struct device *dev);
| ^
1 error generated.
vim +/scsi_block_targets +2912 drivers/scsi/scsi_lib.c
2898
2899 /**
2900 * scsi_block_targets - transition all SCSI child devices to SDEV_BLOCK state
2901 * @dev: a parent device of one or more scsi_target devices
2902 * @shost: the Scsi_Host to which this device belongs
2903 *
2904 * Iterate over all children of @dev, which should be scsi_target devices,
2905 * and switch all subordinate scsi devices to SDEV_BLOCK state. Wait for
2906 * ongoing scsi_queue_rq() calls to finish. May sleep.
2907 *
2908 * Note:
2909 * @dev must not itself be a scsi_target device.
2910 */
2911 void
> 2912 scsi_block_targets(struct device *dev, struct Scsi_Host *shost)
2913 {
2914 WARN_ON_ONCE(scsi_is_target_device(dev));
2915 device_for_each_child(dev, NULL, target_block);
2916 blk_mq_wait_quiesce_done(&shost->tag_set);
2917 }
2918 EXPORT_SYMBOL_GPL(scsi_block_targets);
2919
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-13 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 17:42 [PATCH v6 0/7] scsi: fixes for targets with many LUNs, and scsi_target_block rework mwilck
2023-06-13 17:42 ` [PATCH v6 1/7] bsg: increase number of devices mwilck
2023-06-13 17:42 ` [PATCH v6 2/7] scsi: sg: " mwilck
2023-06-13 17:42 ` [PATCH v6 3/7] scsi: merge scsi_internal_device_block() and device_block() mwilck
2023-06-13 17:42 ` [PATCH v6 4/7] scsi: don't wait for quiesce in scsi_stop_queue() mwilck
2023-06-13 17:42 ` [PATCH v6 5/7] scsi: don't wait for quiesce in scsi_device_block() mwilck
2023-06-13 17:42 ` [PATCH v6 6/7] scsi: replace scsi_target_block() by scsi_block_targets() mwilck
2023-06-13 21:16 ` kernel test robot [this message]
2023-06-14 4:54 ` kernel test robot
2023-06-13 17:42 ` [PATCH v6 7/7] scsi: improve warning message in scsi_device_block() mwilck
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=202306140503.hMWyg8Xa-lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=mwilck@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sebaddel@cisco.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