From: Niklas Cassel <cassel@kernel.org>
To: "Jesper Nilsson" <jesper.nilsson@axis.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>, Frank Li <Frank.Li@nxp.com>,
linux-arm-kernel@axis.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCI endpoint additional pci_epc_set_bar() checks
Date: Fri, 15 Nov 2024 10:01:27 +0100 [thread overview]
Message-ID: <ZzcN56G2MACeJHvo@ryzen> (raw)
In-Reply-To: <20241115084749.1915915-5-cassel@kernel.org>
On Fri, Nov 15, 2024 at 09:47:49AM +0100, Niklas Cassel wrote:
> Hello all,
>
> This series adds some extra checks to ensure that it is not possible to
> program the iATU with an address which we did not intend to use.
>
> If these checks were in place when testing some of the earlier revisions
> of Frank's doorbell patches (which did not handle fixed BARs properly),
> we would gotten an error, rather than silently using an address which we
> did not intend to use.
>
> Having these checks in place will hopefully avoid similar debugging in the
> future.
Changes since v1:
-Improved commit message in patch 3/3.
-Picked up tags.
Kind regards,
Niklas
prev parent reply other threads:[~2024-11-15 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 8:47 [PATCH v2 0/3] PCI endpoint additional pci_epc_set_bar() checks Niklas Cassel
2024-11-15 8:47 ` [PATCH v2 1/3] PCI: artpec6: Implement dw_pcie_ep operation get_features Niklas Cassel
2024-11-15 14:39 ` Jesper Nilsson
2024-11-15 8:47 ` [PATCH v2 2/3] PCI: endpoint: Add size check for fixed size BARs in pci_epc_set_bar() Niklas Cassel
2024-11-15 8:47 ` [PATCH v2 3/3] PCI: dwc: ep: Add 'address' alignment to 'size' check in dw_pcie_prog_ep_inbound_atu() Niklas Cassel
2024-11-15 9:01 ` Niklas Cassel [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=ZzcN56G2MACeJHvo@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=jesper.nilsson@axis.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@axis.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox