From: kernel test robot <lkp@intel.com>
To: Stafford Horne <shorne@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/pci/pci.c:4195 pci_pio_to_address() warn: always true condition '(pio >= (0 - 0)) => (0-u32max >= 0)'
Date: Wed, 28 Jun 2023 21:23:20 +0800 [thread overview]
Message-ID: <202306282106.NdF2Rooc-lkp@intel.com> (raw)
Hi Stafford,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6aeadf7896bff4ca230702daba8788455e6b866e
commit: ded2ee36313c941f1a12b6f85cde295b575264ae openrisc: Add pci bus support
date: 11 months ago
config: openrisc-randconfig-m041-20230628 (https://download.01.org/0day-ci/archive/20230628/202306282106.NdF2Rooc-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230628/202306282106.NdF2Rooc-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/202306282106.NdF2Rooc-lkp@intel.com/
smatch warnings:
drivers/pci/pci.c:4195 pci_pio_to_address() warn: always true condition '(pio >= (0 - 0)) => (0-u32max >= 0)'
drivers/pcmcia/yenta_socket.c:1238 yenta_probe() warn: unsigned 'id->driver_data' is never less than zero.
vim +4195 drivers/pci/pci.c
c5076cfe768998 Tomasz Nowicki 2016-05-11 4189
c5076cfe768998 Tomasz Nowicki 2016-05-11 4190 phys_addr_t pci_pio_to_address(unsigned long pio)
c5076cfe768998 Tomasz Nowicki 2016-05-11 4191 {
c5076cfe768998 Tomasz Nowicki 2016-05-11 4192 phys_addr_t address = (phys_addr_t)OF_BAD_ADDR;
c5076cfe768998 Tomasz Nowicki 2016-05-11 4193
c5076cfe768998 Tomasz Nowicki 2016-05-11 4194 #ifdef PCI_IOBASE
5745392e0c2b78 Zhichang Yuan 2018-03-15 @4195 if (pio >= MMIO_UPPER_LIMIT)
c5076cfe768998 Tomasz Nowicki 2016-05-11 4196 return address;
c5076cfe768998 Tomasz Nowicki 2016-05-11 4197
5745392e0c2b78 Zhichang Yuan 2018-03-15 4198 address = logic_pio_to_hwaddr(pio);
c5076cfe768998 Tomasz Nowicki 2016-05-11 4199 #endif
c5076cfe768998 Tomasz Nowicki 2016-05-11 4200
c5076cfe768998 Tomasz Nowicki 2016-05-11 4201 return address;
c5076cfe768998 Tomasz Nowicki 2016-05-11 4202 }
9cc742078c9a90 Jianjun Wang 2021-04-20 4203 EXPORT_SYMBOL_GPL(pci_pio_to_address);
c5076cfe768998 Tomasz Nowicki 2016-05-11 4204
:::::: The code at line 4195 was first introduced by commit
:::::: 5745392e0c2b78e0d73203281d5c42cbd6993194 PCI: Apply the new generic I/O management on PCI IO hosts
:::::: TO: Zhichang Yuan <yuanzhichang@hisilicon.com>
:::::: CC: Bjorn Helgaas <helgaas@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-06-28 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-14 4:28 drivers/pci/pci.c:4195 pci_pio_to_address() warn: always true condition '(pio >= (0 - 0)) => (0-u32max >= 0)' kernel test robot
2023-01-11 15:40 kernel test robot
2022-09-22 10:44 kernel test robot
2022-09-21 8:09 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=202306282106.NdF2Rooc-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shorne@gmail.com \
/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