public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Karan Tilak Kumar <kartilak@cisco.com>, sebaddel@cisco.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	arulponn@cisco.com, djhawar@cisco.com, gcboffa@cisco.com,
	mkai2@cisco.com, satishkh@cisco.com, aeasi@cisco.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Karan Tilak Kumar <kartilak@cisco.com>
Subject: Re: [PATCH v5 09/14] scsi: fnic: Modify IO path to use FDLS
Date: Mon, 21 Oct 2024 01:28:20 +0800	[thread overview]
Message-ID: <202410210147.fQp7tYeb-lkp@intel.com> (raw)
In-Reply-To: <20241018161409.4442-10-kartilak@cisco.com>

Hi Karan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on mkp-scsi/for-next]
[cannot apply to jejb-scsi/for-next linus/master v6.12-rc3 next-20241018]
[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/Karan-Tilak-Kumar/scsi-fnic-Replace-shost_printk-with-dev_info-dev_err/20241019-002800
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link:    https://lore.kernel.org/r/20241018161409.4442-10-kartilak%40cisco.com
patch subject: [PATCH v5 09/14] scsi: fnic: Modify IO path to use FDLS
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20241021/202410210147.fQp7tYeb-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241021/202410210147.fQp7tYeb-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/202410210147.fQp7tYeb-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/scsi/fnic/fnic_scsi.c:269:15: warning: variable 'ioreq_count' set but not used [-Wunused-but-set-variable]
     269 |         unsigned int ioreq_count;
         |                      ^
   drivers/scsi/fnic/fnic_scsi.c:928:6: warning: variable 'xfer_len' set but not used [-Wunused-but-set-variable]
     928 |         u64 xfer_len = 0;
         |             ^
   drivers/scsi/fnic/fnic_scsi.c:2506:21: warning: variable 'fnic_stats' set but not used [-Wunused-but-set-variable]
    2506 |         struct fnic_stats *fnic_stats;
         |                            ^
   3 warnings generated.


vim +/ioreq_count +269 drivers/scsi/fnic/fnic_scsi.c

   258	
   259	
   260	/*
   261	 * fnic_fw_reset_handler
   262	 * Routine to send reset msg to fw
   263	 */
   264	int fnic_fw_reset_handler(struct fnic *fnic)
   265	{
   266		struct vnic_wq_copy *wq = &fnic->hw_copy_wq[0];
   267		int ret = 0;
   268		unsigned long flags;
 > 269		unsigned int ioreq_count;
   270	
   271		/* indicate fwreset to io path */
   272		fnic_set_state_flags(fnic, FNIC_FLAGS_FWRESET);
   273		ioreq_count = fnic_count_all_ioreqs(fnic);
   274	
   275		/* wait for io cmpl */
   276		while (atomic_read(&fnic->in_flight))
   277			schedule_timeout(msecs_to_jiffies(1));
   278	
   279		spin_lock_irqsave(&fnic->wq_copy_lock[0], flags);
   280	
   281		if (vnic_wq_copy_desc_avail(wq) <= fnic->wq_copy_desc_low[0])
   282			free_wq_copy_descs(fnic, wq, 0);
   283	
   284		if (!vnic_wq_copy_desc_avail(wq))
   285			ret = -EAGAIN;
   286		else {
   287			fnic_queue_wq_copy_desc_fw_reset(wq, SCSI_NO_TAG);
   288			atomic64_inc(&fnic->fnic_stats.fw_stats.active_fw_reqs);
   289			if (atomic64_read(&fnic->fnic_stats.fw_stats.active_fw_reqs) >
   290				  atomic64_read(&fnic->fnic_stats.fw_stats.max_fw_reqs))
   291				atomic64_set(&fnic->fnic_stats.fw_stats.max_fw_reqs,
   292					atomic64_read(
   293					  &fnic->fnic_stats.fw_stats.active_fw_reqs));
   294		}
   295	
   296		spin_unlock_irqrestore(&fnic->wq_copy_lock[0], flags);
   297	
   298		if (!ret) {
   299			atomic64_inc(&fnic->fnic_stats.reset_stats.fw_resets);
   300			FNIC_SCSI_DBG(KERN_INFO, fnic->lport->host, fnic->fnic_num,
   301					"Issued fw reset\n");
   302		} else {
   303			fnic_clear_state_flags(fnic, FNIC_FLAGS_FWRESET);
   304			FNIC_SCSI_DBG(KERN_ERR, fnic->lport->host, fnic->fnic_num,
   305					"Failed to issue fw reset\n");
   306		}
   307	
   308		return ret;
   309	}
   310	

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

  reply	other threads:[~2024-10-20 17:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 16:13 [PATCH v5 00/14] Introduce support for Fabric Discovery and Karan Tilak Kumar
2024-10-18 16:13 ` [PATCH v5 01/14] scsi: fnic: Replace shost_printk with dev_info/dev_err Karan Tilak Kumar
2024-10-21  6:34   ` Hannes Reinecke
2024-10-18 16:13 ` [PATCH v5 02/14] scsi: fnic: Add headers and definitions for FDLS Karan Tilak Kumar
2024-10-21  6:33   ` Hannes Reinecke
2024-10-21 23:44     ` Karan Tilak Kumar (kartilak)
2024-10-18 16:13 ` [PATCH v5 03/14] scsi: fnic: Add support for fabric based solicited requests and responses Karan Tilak Kumar
2024-10-21  7:16   ` Hannes Reinecke
2024-10-22  0:03     ` Karan Tilak Kumar (kartilak)
2024-10-18 16:13 ` [PATCH v5 04/14] scsi: fnic: Add support for target " Karan Tilak Kumar
2024-10-24  7:28   ` Hannes Reinecke
2024-10-29  0:37     ` Karan Tilak Kumar (kartilak)
2024-10-18 16:14 ` [PATCH v5 05/14] scsi: fnic: Add support for unsolicited " Karan Tilak Kumar
2024-10-24  7:13   ` Hannes Reinecke
2024-10-29  0:42     ` Karan Tilak Kumar (kartilak)
2024-10-18 16:14 ` [PATCH v5 06/14] scsi: fnic: Add and integrate support for FDMI Karan Tilak Kumar
2024-10-24  7:32   ` Hannes Reinecke
2024-10-29  0:48     ` Karan Tilak Kumar (kartilak)
2024-10-18 16:14 ` [PATCH v5 07/14] scsi: fnic: Add and integrate support for FIP Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 08/14] scsi: fnic: Add functionality in fnic to support FDLS Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 09/14] scsi: fnic: Modify IO path to use FDLS Karan Tilak Kumar
2024-10-20 17:28   ` kernel test robot [this message]
2024-10-24  7:04   ` Hannes Reinecke
2024-10-29  0:54     ` Karan Tilak Kumar (kartilak)
2024-11-20  0:03       ` Karan Tilak Kumar (kartilak)
2024-10-18 16:14 ` [PATCH v5 10/14] scsi: fnic: Modify fnic interfaces " Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 11/14] scsi: fnic: Add stats and related functionality Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 12/14] scsi: fnic: Code cleanup Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 13/14] scsi: fnic: Add support to handle port channel RSCN Karan Tilak Kumar
2024-10-18 16:14 ` [PATCH v5 14/14] scsi: fnic: Increment driver version Karan Tilak Kumar

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=202410210147.fQp7tYeb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aeasi@cisco.com \
    --cc=arulponn@cisco.com \
    --cc=djhawar@cisco.com \
    --cc=gcboffa@cisco.com \
    --cc=jejb@linux.ibm.com \
    --cc=kartilak@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.petersen@oracle.com \
    --cc=mkai2@cisco.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=satishkh@cisco.com \
    --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