From: kernel test robot <lkp@intel.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>,
jgg@ziepe.ca, dledford@redhat.com
Cc: kbuild-all@lists.01.org, linux-rdma@vger.kernel.org,
Selvin Xavier <selvin.xavier@broadcom.com>,
Naresh Kumar PBS <nareshkumar.pbs@broadcom.com>,
Devesh Sharma <devesh.sharma@broadcom.com>
Subject: Re: [PATCH for-next] RDMA/bnxt_re: Move device to error state upon device crash
Date: Wed, 17 Mar 2021 15:53:57 +0800 [thread overview]
Message-ID: <202103171556.ID0OnWKk-lkp@intel.com> (raw)
In-Reply-To: <1615957789-30077-1-git-send-email-selvin.xavier@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 3425 bytes --]
Hi Selvin,
I love your patch! Perhaps something to improve:
[auto build test WARNING on rdma/for-next]
[also build test WARNING on v5.12-rc3 next-20210316]
[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]
url: https://github.com/0day-ci/linux/commits/Selvin-Xavier/RDMA-bnxt_re-Move-device-to-error-state-upon-device-crash/20210317-131222
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.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/0day-ci/linux/commit/3e89320b3476467ccb141c6b5e46c1615f010b66
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Selvin-Xavier/RDMA-bnxt_re-Move-device-to-error-state-upon-device-crash/20210317-131222
git checkout 3e89320b3476467ccb141c6b5e46c1615f010b66
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/infiniband/hw/bnxt_re/main.c: In function 'bnxt_re_stop':
>> drivers/infiniband/hw/bnxt_re/main.c:226:26: warning: variable 'rcfw' set but not used [-Wunused-but-set-variable]
226 | struct bnxt_qplib_rcfw *rcfw;
| ^~~~
vim +/rcfw +226 drivers/infiniband/hw/bnxt_re/main.c
221
222 /* for handling bnxt_en callbacks later */
223 static void bnxt_re_stop(void *p)
224 {
225 struct bnxt_re_dev *rdev = p;
> 226 struct bnxt_qplib_rcfw *rcfw;
227 struct bnxt *bp;
228
229 if (!rdev)
230 return;
231 ASSERT_RTNL();
232
233 /* L2 driver invokes this callback during device error/crash or device
234 * reset. Current RoCE driver doesn't recover the device in case of
235 * error. Handle the error by dispatching fatal events to all qps
236 * ie. by calling bnxt_re_dev_stop and release the MSIx vectors as
237 * L2 driver want to modify the MSIx table.
238 */
239 bp = netdev_priv(rdev->netdev);
240 rcfw = &rdev->rcfw;
241
242 ibdev_info(&rdev->ibdev, "Handle device stop call from L2 driver");
243 /* Check the current device state from L2 structure and move the
244 * device to detached state if FW_FATAL_COND is set.
245 * This prevents more commands to HW during clean-up,
246 * in case the device is already in error.
247 */
248 if (test_bit(BNXT_STATE_FW_FATAL_COND, &bp->state))
249 set_bit(ERR_DEVICE_DETACHED, &rdev->rcfw.cmdq.flags);
250
251 bnxt_re_dev_stop(rdev);
252 bnxt_re_stop_irq(rdev);
253 /* Move the device states to detached and avoid sending any more
254 * commands to HW
255 */
256 set_bit(BNXT_RE_FLAG_ERR_DEVICE_DETACHED, &rdev->flags);
257 set_bit(ERR_DEVICE_DETACHED, &rdev->rcfw.cmdq.flags);
258 }
259
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 72686 bytes --]
prev parent reply other threads:[~2021-03-17 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 5:09 [PATCH for-next] RDMA/bnxt_re: Move device to error state upon device crash Selvin Xavier
2021-03-17 7:53 ` kernel test robot [this message]
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=202103171556.ID0OnWKk-lkp@intel.com \
--to=lkp@intel.com \
--cc=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kbuild-all@lists.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nareshkumar.pbs@broadcom.com \
--cc=selvin.xavier@broadcom.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