From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Jonas Gorski <jonas.gorski@gmail.com>
Subject: Re: [PATCH v1 1/1] PCI: Avoid potential out-of-bounds read in pci_dev_for_each_resource()
Date: Mon, 20 Nov 2023 16:48:41 -0600 [thread overview]
Message-ID: <170052045488.221134.10607846623065848997.b4-ty@google.com> (raw)
In-Reply-To: <20231030114218.2752236-1-andriy.shevchenko@linux.intel.com>
From: Bjorn Helgaas <bhelgaas@google.com>
On Mon, 30 Oct 2023 13:42:18 +0200, Andy Shevchenko wrote:
> Coverity complains that pointer in the pci_dev_for_each_resource()
> may be wrong, i.e. mighe be used for the out-of-bounds read.
>
> There is no actual issue right now, because we have another check
> afterwards and the out-of-bounds read is not being performed. In any
> case it's better code with this get fixed, hence the proposed change.
>
> [...]
Applied to "resource" for v6.8, thanks!
[1/1] PCI: Avoid potential out-of-bounds read in pci_dev_for_each_resource()
commit: 3171e46d677a668eed3086da78671f1e4f5b8405
Best regards,
--
Bjorn Helgaas <bhelgaas@google.com>
prev parent reply other threads:[~2023-11-20 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 11:42 [PATCH v1 1/1] PCI: Avoid potential out-of-bounds read in pci_dev_for_each_resource() Andy Shevchenko
2023-11-03 18:46 ` Bjorn Helgaas
2023-11-13 11:49 ` Andy Shevchenko
2023-11-20 22:48 ` 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=170052045488.221134.10607846623065848997.b4-ty@google.com \
--to=helgaas@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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.