From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [luxis1999-iommufd:iommufd-v5.18-rc4-nesting 37/70] drivers/iommu/iommufd/vfio_compat.c:494:2-8: preceding lock on line 491
Date: Wed, 15 Jun 2022 08:33:40 +0800 [thread overview]
Message-ID: <202206150817.8ZznTMcP-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
TO: Liu Yi L <yi.l.liu@intel.com>
tree: https://github.com/luxis1999/iommufd iommufd-v5.18-rc4-nesting
head: e642747ca46aa568063964b5b5101e35258ea0d5
commit: f3c739aa1a7a8ff80f9997f02d36f2a63f53a251 [37/70] iommufd: Add vfio_group_set/unset_iommufd helpers
:::::: branch date: 2 days ago
:::::: commit date: 6 weeks ago
config: x86_64-randconfig-c002-20220613 (https://download.01.org/0day-ci/archive/20220615/202206150817.8ZznTMcP-lkp(a)intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
cocci warnings: (new ones prefixed by >>)
>> drivers/iommu/iommufd/vfio_compat.c:494:2-8: preceding lock on line 491
vim +494 drivers/iommu/iommufd/vfio_compat.c
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 481
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 482 void vfio_group_unset_iommufd(void *iommufd, struct list_head *device_list)
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 483 {
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 484 struct iommufd_ctx *ictx = (struct iommufd_ctx *)iommufd;
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 485 struct iommufd_ioas *ioas;
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 486 struct vfio_device *device;
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 487 unsigned int ioas_id;
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 488
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 489 if (!ictx)
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 490 return;
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 @491 mutex_lock(&ictx->vfio_compat);
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 492 ioas = get_compat_ioas(ictx);
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 493 if (IS_ERR(ioas))
f3c739aa1a7a8ff Nicolin Chen 2022-01-31 @494 return;
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-15 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 0:33 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-15 4:07 [luxis1999-iommufd:iommufd-v5.18-rc4-nesting 37/70] drivers/iommu/iommufd/vfio_compat.c:494:2-8: preceding lock on line 491 kernel test robot
2022-06-15 6:14 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=202206150817.8ZznTMcP-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.