From: kernel test robot <lkp@intel.com>
To: Chathura Rajapaksha <chathura.abeyrathne.lk@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] audit accesses to unassigned PCI config regions
Date: Sun, 27 Apr 2025 07:32:25 +0800 [thread overview]
Message-ID: <202504270713.ZepwWC7B-lkp@intel.com> (raw)
In-Reply-To: <20250426212253.40473-3-chath@bu.edu>
Hi Chathura,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on f1a3944c860b0615d0513110d8cf62bb94adbb41]
url: https://github.com/intel-lab-lkp/linux/commits/Chathura-Rajapaksha/block-accesses-to-unassigned-PCI-config-regions/20250427-052942
base: f1a3944c860b0615d0513110d8cf62bb94adbb41
patch link: https://lore.kernel.org/r/20250426212253.40473-3-chath%40bu.edu
patch subject: [RFC PATCH 2/2] audit accesses to unassigned PCI config regions
config: arm-randconfig-003-20250427 (https://download.01.org/0day-ci/archive/20250427/202504270713.ZepwWC7B-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250427/202504270713.ZepwWC7B-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/202504270713.ZepwWC7B-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/vfio/pci/vfio_pci_config.c:2011:32: warning: format specifies type 'long' but the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
2008 | "device=%04x:%02x:%02x.%d access=%s offset=0x%llx size=%ld blocked=%u\n",
| ~~~
| %zu
2009 | pci_domain_nr(pdev->bus), pdev->bus->number,
2010 | PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn),
2011 | vfio_audit_str[op], *ppos, count, blocked);
| ^~~~~
1 warning generated.
vim +2011 drivers/vfio/pci/vfio_pci_config.c
1994
1995 static void vfio_audit_access(const struct pci_dev *pdev,
1996 size_t count, loff_t *ppos, bool blocked, unsigned int op)
1997 {
1998 struct audit_buffer *ab;
1999
2000 if (WARN_ON_ONCE(op >= VFIO_AUDIT_MAX))
2001 return;
2002 if (audit_enabled == AUDIT_OFF)
2003 return;
2004 ab = audit_log_start(audit_context(), GFP_ATOMIC, AUDIT_VFIO);
2005 if (unlikely(!ab))
2006 return;
2007 audit_log_format(ab,
2008 "device=%04x:%02x:%02x.%d access=%s offset=0x%llx size=%ld blocked=%u\n",
2009 pci_domain_nr(pdev->bus), pdev->bus->number,
2010 PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn),
> 2011 vfio_audit_str[op], *ppos, count, blocked);
2012 audit_log_end(ab);
2013 }
2014
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-04-26 23:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250426212253.40473-3-chath@bu.edu>]
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=202504270713.ZepwWC7B-lkp@intel.com \
--to=lkp@intel.com \
--cc=chathura.abeyrathne.lk@gmail.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox