From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [trondmy-nfs-2.6:linux-next 59/66] net/sunrpc/xprt.c:1690:18-28: ERROR: function xprt_dynamic_alloc_slot called on line 1728 inside lock on line 1722 but uses GFP_KERNEL
Date: Mon, 14 Mar 2022 11:41:33 +0800 [thread overview]
Message-ID: <202203141129.Lt2sd2kq-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
CC: linux-kernel(a)vger.kernel.org
TO: NeilBrown <neilb@suse.de>
CC: Trond Myklebust <trond.myklebust@hammerspace.com>
tree: git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git linux-next
head: 693486d5f8951780a9bb31f7fe935171a80010e4
commit: a721035477fb5fb8abc738fbe410b07c12af3dc5 [59/66] SUNRPC/xprt: async tasks mustn't block waiting for memory
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20220314/202203141129.Lt2sd2kq-lkp(a)intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.2.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>
cocci warnings: (new ones prefixed by >>)
>> net/sunrpc/xprt.c:1690:18-28: ERROR: function xprt_dynamic_alloc_slot called on line 1728 inside lock on line 1722 but uses GFP_KERNEL
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-03-14 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 3:41 kernel test robot [this message]
2022-03-14 3:32 ` [PATCH] SUNRPC/xprt: 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=202203141129.Lt2sd2kq-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.