From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android13-5.10-2026-10 1/1] drivers/vfio/vfio.c:527: warning: Function parameter or member 'device' not described in 'vfio_device_put'
Date: Mon, 19 Oct 2026 20:25:11 +0200 [thread overview]
Message-ID: <202610192036.15w73rFB-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android13-5.10-2026-10
head: a4c2f82969bc5fa7fcc21ede4b690ece7ff72335
commit: a2fbf4acd28069d4922c33e4b5b0d58fc38073f8 [1/1] vfio: Split creation of a vfio_device into init and register ops
config: arm-randconfig-r2104-20261018 (https://download.01.org/0day-ci/archive/20261019/202610192036.15w73rFB-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261019/202610192036.15w73rFB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610192036.15w73rFB-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/vfio/vfio.c:214: warning: Function parameter or member 'ops' not described in 'vfio_register_iommu_driver'
drivers/vfio/vfio.c:263: warning: Function parameter or member 'group' not described in 'vfio_alloc_group_minor'
drivers/vfio/vfio.c:283: warning: Function parameter or member 'container' not described in 'vfio_container_get'
drivers/vfio/vfio.c:315: warning: Function parameter or member 'iommu_group' not described in 'vfio_create_group'
>> drivers/vfio/vfio.c:527: warning: Function parameter or member 'device' not described in 'vfio_device_put'
drivers/vfio/vfio.c:633: warning: Function parameter or member 'group' not described in 'vfio_group_nb_add_dev'
drivers/vfio/vfio.c:633: warning: Function parameter or member 'dev' not described in 'vfio_group_nb_add_dev'
>> drivers/vfio/vfio.c:745: warning: Function parameter or member 'device' not described in 'vfio_init_group_dev'
>> drivers/vfio/vfio.c:745: warning: Function parameter or member 'dev' not described in 'vfio_init_group_dev'
>> drivers/vfio/vfio.c:745: warning: Function parameter or member 'ops' not described in 'vfio_init_group_dev'
>> drivers/vfio/vfio.c:745: warning: Function parameter or member 'device_data' not described in 'vfio_init_group_dev'
drivers/vfio/vfio.c:833: warning: Function parameter or member 'dev' not described in 'vfio_device_get_from_dev'
drivers/vfio/vfio.c:982: warning: Function parameter or member 'container' not described in 'vfio_ioctl_check_extension'
drivers/vfio/vfio.c:982: warning: Function parameter or member 'arg' not described in 'vfio_ioctl_check_extension'
drivers/vfio/vfio.c:1253: warning: Function parameter or member 'group' not described in '__vfio_group_unset_container'
drivers/vfio/vfio.c:1588: warning: Function parameter or member 'inode' not described in 'vfio_device_fops_release'
drivers/vfio/vfio.c:1588: warning: Function parameter or member 'filep' not described in 'vfio_device_fops_release'
drivers/vfio/vfio.c:1682: warning: Function parameter or member 'filep' not described in 'vfio_group_get_external_user'
drivers/vfio/vfio.c:1719: warning: Function parameter or member 'dev' not described in 'vfio_group_get_external_user_from_dev'
drivers/vfio/vfio.c:1779: warning: Function parameter or member 'caps' not described in 'vfio_info_cap_add'
drivers/vfio/vfio.c:1779: warning: Function parameter or member 'size' not described in 'vfio_info_cap_add'
drivers/vfio/vfio.c:1779: warning: Function parameter or member 'id' not described in 'vfio_info_cap_add'
drivers/vfio/vfio.c:1779: warning: Function parameter or member 'version' not described in 'vfio_info_cap_add'
drivers/vfio/vfio.c:2298: warning: Function parameter or member 'dev' not described in 'vfio_devnode'
drivers/vfio/vfio.c:2298: warning: Function parameter or member 'mode' not described in 'vfio_devnode'
vim +527 drivers/vfio/vfio.c
7ed3ea8a71187a Kirti Wankhede 2016-11-17 521
cba3345cc494ad Alex Williamson 2012-07-31 522 /**
cba3345cc494ad Alex Williamson 2012-07-31 523 * Device objects - create, release, get, put, search
cba3345cc494ad Alex Williamson 2012-07-31 524 */
cba3345cc494ad Alex Williamson 2012-07-31 525 /* Device reference always implies a group reference */
44f507163d9e51 Vijay Mohan Pandarathil 2013-03-11 526 void vfio_device_put(struct vfio_device *device)
cba3345cc494ad Alex Williamson 2012-07-31 @527 {
f54fa910e6cb5b Jason Gunthorpe 2021-03-30 528 if (refcount_dec_and_test(&device->refcount))
f54fa910e6cb5b Jason Gunthorpe 2021-03-30 529 complete(&device->comp);
cba3345cc494ad Alex Williamson 2012-07-31 530 }
44f507163d9e51 Vijay Mohan Pandarathil 2013-03-11 531 EXPORT_SYMBOL_GPL(vfio_device_put);
cba3345cc494ad Alex Williamson 2012-07-31 532
:::::: The code at line 527 was first introduced by commit
:::::: cba3345cc494ad286ca8823f44b2c16cae496679 vfio: VFIO core
:::::: TO: Alex Williamson <alex.williamson@redhat.com>
:::::: CC: Alex Williamson <alex.williamson@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-19 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610192036.15w73rFB-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.