From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [rdma:wip/jgg-for-next 13/14] drivers/infiniband/sw/rxe/rxe_pool.c:360:21-31: ERROR: function rxe_alloc_nl called on line 385 inside lock on line 384 but uses GFP_KERNEL
Date: Thu, 14 Jan 2021 23:58:32 +0800 [thread overview]
Message-ID: <202101142325.3vKm3sdG-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
CC: kbuild-all(a)lists.01.org
CC: Doug Ledford <dledford@redhat.com>
CC: Jason Gunthorpe <jgg+lists@ziepe.ca>
CC: linux-rdma(a)vger.kernel.org
TO: Bob Pearson <rpearsonhpe@gmail.com>
CC: Jason Gunthorpe <jgg@nvidia.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git wip/jgg-for-next
head: 8a48ac7f6c24973863b42d03156d5e34c46c2971
commit: 3853c35e243d56238159e8365b6aca410bdd4576 [13/14] RDMA/rxe: Add unlocked versions of pool APIs
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: x86_64-randconfig-c002-20210114 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
"coccinelle warnings: (new ones prefixed by >>)"
>> drivers/infiniband/sw/rxe/rxe_pool.c:360:21-31: ERROR: function rxe_alloc_nl called on line 385 inside lock on line 384 but uses GFP_KERNEL
Please review and possibly fold the followup patch.
---
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: 36942 bytes --]
next reply other threads:[~2021-01-14 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 15:58 kernel test robot [this message]
2021-01-14 15:58 ` [PATCH] RDMA/rxe: fix call_kern.cocci warnings kernel test robot
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=202101142325.3vKm3sdG-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.