From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, mitchell.augustin@canonical.com,
ilpo.jarvinen@linux.intel.com, david.laight.linux@gmail.com,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2] PCI: Fix BUILD_BUG_ON usage for old gcc
Date: Wed, 12 Feb 2025 16:18:49 -0600 [thread overview]
Message-ID: <20250212221849.GA93700@bhelgaas> (raw)
In-Reply-To: <20250212185337.293023-1-alex.williamson@redhat.com>
On Wed, Feb 12, 2025 at 11:53:32AM -0700, Alex Williamson wrote:
> As reported in the below link, it seems older versions of gcc cannot
> determine that the howmany variable is known for all callers. Include
> a test so that newer compilers can enforce this sanity check and older
> compilers can still work. Add __always_inline attribute to give the
> compiler an even better chance to know the inputs.
>
> Fixes: 4453f360862e ("PCI: Batch BAR sizing operations")
> Link: https://lore.kernel.org/all/20250209154512.GA18688@redhat.com
> Reported-by: Oleg Nesterov <oleg@redhat.com>
> Tested-by: Oleg Nesterov <oleg@redhat.com>
> Tested-by: Mitchell Augustin <mitchell.augustin@canonical.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Applied to pci/for-linus for v6.14 since this fixes a build issue we
added in v6.14-rc1, thanks, Alex.
> ---
>
> v2:
> - Switch to statically_true (David Laight)
> - Add __always_inline (David Laight)
> - Included Tested-by reports
>
> drivers/pci/probe.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index b6536ed599c3..246744d8d268 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -339,13 +339,14 @@ int __pci_read_base(struct pci_dev *dev, enum pci_bar_type type,
> return (res->flags & IORESOURCE_MEM_64) ? 1 : 0;
> }
>
> -static void pci_read_bases(struct pci_dev *dev, unsigned int howmany, int rom)
> +static __always_inline void pci_read_bases(struct pci_dev *dev,
> + unsigned int howmany, int rom)
> {
> u32 rombar, stdbars[PCI_STD_NUM_BARS];
> unsigned int pos, reg;
> u16 orig_cmd;
>
> - BUILD_BUG_ON(howmany > PCI_STD_NUM_BARS);
> + BUILD_BUG_ON(statically_true(howmany > PCI_STD_NUM_BARS));
>
> if (dev->non_compliant_bars)
> return;
> --
> 2.48.1
>
prev parent reply other threads:[~2025-02-12 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:53 [PATCH v2] PCI: Fix BUILD_BUG_ON usage for old gcc Alex Williamson
2025-02-12 22:18 ` Bjorn Helgaas [this message]
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=20250212221849.GA93700@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=david.laight.linux@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mitchell.augustin@canonical.com \
--cc=oleg@redhat.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