From: kernel test robot <lkp@intel.com>
To: Nilesh Javali <njavali@marvell.com>, martin.petersen@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, linux-scsi@vger.kernel.org,
GR-QLogic-Storage-Upstream@marvell.com, bhazarika@marvell.com,
agurumurthy@marvell.com, sdeodhar@marvell.com
Subject: Re: [PATCH 1/7] qla2xxx: Multi-que support for TMF
Date: Thu, 27 Apr 2023 18:04:35 +0800 [thread overview]
Message-ID: <202304271702.GpIL391S-lkp@intel.com> (raw)
In-Reply-To: <20230427080351.9889-2-njavali@marvell.com>
Hi Nilesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c8e22b7a1694bb8d025ea636816472739d859145]
url: https://github.com/intel-lab-lkp/linux/commits/Nilesh-Javali/qla2xxx-Multi-que-support-for-TMF/20230427-160555
base: c8e22b7a1694bb8d025ea636816472739d859145
patch link: https://lore.kernel.org/r/20230427080351.9889-2-njavali%40marvell.com
patch subject: [PATCH 1/7] qla2xxx: Multi-que support for TMF
config: ia64-allyesconfig (https://download.01.org/0day-ci/archive/20230427/202304271702.GpIL391S-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 12.1.0
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://github.com/intel-lab-lkp/linux/commit/b9e8bdc4cd77acae5886c7c447d34d898bd1d821
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nilesh-Javali/qla2xxx-Multi-que-support-for-TMF/20230427-160555
git checkout b9e8bdc4cd77acae5886c7c447d34d898bd1d821
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/scsi/qla2xxx/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304271702.GpIL391S-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/scsi/qla2xxx/qla_init.c:2024:1: warning: no previous prototype for '__qla2x00_async_tm_cmd' [-Wmissing-prototypes]
2024 | __qla2x00_async_tm_cmd(struct tmf_arg *arg)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/__qla2x00_async_tm_cmd +2024 drivers/scsi/qla2xxx/qla_init.c
2022
2023 int
> 2024 __qla2x00_async_tm_cmd(struct tmf_arg *arg)
2025 {
2026 struct scsi_qla_host *vha = arg->vha;
2027 struct srb_iocb *tm_iocb;
2028 srb_t *sp;
2029 unsigned long flags;
2030 int rval = QLA_FUNCTION_FAILED;
2031
2032 fc_port_t *fcport = arg->fcport;
2033
2034 /* ref: INIT */
2035 sp = qla2xxx_get_qpair_sp(vha, arg->qpair, fcport, GFP_KERNEL);
2036 if (!sp)
2037 goto done;
2038
2039 qla_vha_mark_busy(vha);
2040 sp->type = SRB_TM_CMD;
2041 sp->name = "tmf";
2042 qla2x00_init_async_sp(sp, qla2x00_get_async_timeout(vha),
2043 qla2x00_tmf_sp_done);
2044 sp->u.iocb_cmd.timeout = qla2x00_tmf_iocb_timeout;
2045
2046 tm_iocb = &sp->u.iocb_cmd;
2047 init_completion(&tm_iocb->u.tmf.comp);
2048 tm_iocb->u.tmf.flags = arg->flags;
2049 tm_iocb->u.tmf.lun = arg->lun;
2050
2051 rval = qla2x00_start_sp(sp);
2052 ql_dbg(ql_dbg_taskm, vha, 0x802f,
2053 "Async-tmf hdl=%x loop-id=%x portid=%02x%02x%02x ctrl=%x.\n",
2054 sp->handle, fcport->loop_id, fcport->d_id.b.domain,
2055 fcport->d_id.b.area, fcport->d_id.b.al_pa, arg->flags);
2056
2057 if (rval != QLA_SUCCESS)
2058 goto done_free_sp;
2059 wait_for_completion(&tm_iocb->u.tmf.comp);
2060
2061 rval = tm_iocb->u.tmf.data;
2062
2063 if (rval != QLA_SUCCESS) {
2064 ql_log(ql_log_warn, vha, 0x8030,
2065 "TM IOCB failed (%x).\n", rval);
2066 }
2067
2068 if (!test_bit(UNLOADING, &vha->dpc_flags) && !IS_QLAFX00(vha->hw)) {
2069 flags = tm_iocb->u.tmf.flags;
2070 if (flags & (TCF_LUN_RESET|TCF_ABORT_TASK_SET|
2071 TCF_CLEAR_TASK_SET|TCF_CLEAR_ACA))
2072 flags = MK_SYNC_ID_LUN;
2073 else
2074 flags = MK_SYNC_ID;
2075
2076 qla2x00_marker(vha, sp->qpair,
2077 sp->fcport->loop_id, arg->lun, flags);
2078 }
2079
2080 done_free_sp:
2081 /* ref: INIT */
2082 kref_put(&sp->cmd_kref, qla2x00_sp_release);
2083 done:
2084 return rval;
2085 }
2086
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-27 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 8:03 [PATCH 0/7] qla2xxx driver update Nilesh Javali
2023-04-27 8:03 ` [PATCH 1/7] qla2xxx: Multi-que support for TMF Nilesh Javali
2023-04-27 10:04 ` kernel test robot [this message]
2023-04-27 8:03 ` [PATCH 2/7] qla2xxx: Fix task management cmd failure Nilesh Javali
2023-04-27 11:06 ` kernel test robot
2023-04-27 8:03 ` [PATCH 3/7] qla2xxx: Fix task management cmd fail due to unavailable resource Nilesh Javali
2023-04-27 11:48 ` kernel test robot
2023-04-27 8:03 ` [PATCH 4/7] qla2xxx: Fix hang in task management Nilesh Javali
2023-04-27 8:03 ` [PATCH 5/7] qla2xxx: Fix mem access after free Nilesh Javali
2023-04-27 8:03 ` [PATCH 6/7] qla2xxx: Wait for io return on terminate rport Nilesh Javali
2023-04-27 8:03 ` [PATCH 7/7] qla2xxx: Update version to 10.02.08.300-k Nilesh Javali
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=202304271702.GpIL391S-lkp@intel.com \
--to=lkp@intel.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=agurumurthy@marvell.com \
--cc=bhazarika@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sdeodhar@marvell.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 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.