All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [linux-next:master 10689/12912] drivers/infiniband/hw/hfi1/netdev_rx.c:335 hfi1_netdev_free() error: use free_netdev() here instead of kfree(dd->dummy_netdev)
Date: Wed, 27 May 2020 01:52:24 +0800	[thread overview]
Message-ID: <202005270121.n0K4EUO0%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2489 bytes --]

CC: kbuild-all(a)lists.01.org
TO: Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>
CC: Jason Gunthorpe <jgg@mellanox.com>
CC: Mike Marciniszyn <mike.marciniszyn@intel.com>
CC: Dennis Dalessandro <dennis.dalessandro@intel.com>
CC: Sadanand Warrier <sadanand.warrier@intel.com>
CC: Kaike Wan <kaike.wan@intel.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   b0523c7b1c9d0edcd6c0fe6d2cb558a9ad5c60a8
commit: 370caa5b5880cd988645735c2d5d1d597c258e39 [10689/12912] IB/hfi1: Add rx functions for dummy netdev
:::::: branch date: 7 hours ago
:::::: commit date: 5 days ago
config: x86_64-randconfig-m001-20200526 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>

smatch warnings:
drivers/infiniband/hw/hfi1/netdev_rx.c:335 hfi1_netdev_free() error: use free_netdev() here instead of kfree(dd->dummy_netdev)

# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=370caa5b5880cd988645735c2d5d1d597c258e39
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git remote update linux-next
git checkout 370caa5b5880cd988645735c2d5d1d597c258e39
vim +335 drivers/infiniband/hw/hfi1/netdev_rx.c

370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  327  
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  328  void hfi1_netdev_free(struct hfi1_devdata *dd)
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  329  {
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  330  	struct hfi1_netdev_priv *priv;
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  331  
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  332  	if (dd->dummy_netdev) {
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  333  		priv = hfi1_netdev_priv(dd->dummy_netdev);
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  334  		dd_dev_info(dd, "hfi1 netdev freed\n");
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11 @335  		kfree(dd->dummy_netdev);
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  336  		dd->dummy_netdev = NULL;
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  337  	}
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  338  }
370caa5b5880cd9 Grzegorz Andrejczuk 2020-05-11  339  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 43414 bytes --]

             reply	other threads:[~2020-05-26 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 17:52 kbuild test robot [this message]
2020-05-27 19:09 [linux-next:master 10689/12912] drivers/infiniband/hw/hfi1/netdev_rx.c:335 hfi1_netdev_free() error: use free_netdev() here instead of kfree(dd->dummy_netdev) Dan Carpenter
2020-05-27 19:09 ` Dan Carpenter

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=202005270121.n0K4EUO0%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild@lists.01.org \
    /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.