From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PING^3][PATCH v2] PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge
Date: Thu, 31 Mar 2022 08:11:19 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2203310031210.44113@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2203012338460.46819@angie.orcam.me.uk>
On Wed, 2 Mar 2022, Maciej W. Rozycki wrote:
> > > Fix an issue with the Tyan Tomcat IV S1564D system, the BIOS of which
> > > does not assign PCI buses beyond #2, where our resource reallocation
> > > code preserves the reset default of an I/O BAR assignment outside its
> > > upstream PCI-to-PCI bridge's I/O forwarding range for device 06:08.0 in
> > > this log:
> >
> > Would you mind collecting the complete dmesg log before your patch?
> > It's hard to get the entire picture from snippets.
>
> Sure, here's the original log from at the time when I made the patch. I
> think it's as verbose as you can get; there's no way I could have used it
> for the change description.
>
> Also I doubt it should matter, but if you need a fresh log instead from
> 5.17, then I can make one too, but that will take a bit. Let me know if
> you need me to try anything else too.
Ping for:
<https://lore.kernel.org/all/alpine.DEB.2.21.2202010150100.58572@angie.orcam.me.uk/>
Do you need any further information?
Maciej
next prev parent reply other threads:[~2022-03-31 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 10:51 [RESEND][PATCH v2] PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge Maciej W. Rozycki
2022-02-15 21:29 ` [PING][PATCH " Maciej W. Rozycki
2022-03-01 20:43 ` [PING^2][PATCH " Maciej W. Rozycki
2022-03-01 23:15 ` [RESEND][PATCH " Bjorn Helgaas
2022-03-02 0:01 ` Maciej W. Rozycki
2022-03-31 7:11 ` Maciej W. Rozycki [this message]
2022-04-13 22:53 ` [PING^4][PATCH " Maciej W. Rozycki
2022-04-19 22:50 ` [RESEND][PATCH " Bjorn Helgaas
2022-09-17 21:51 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2203310031210.44113@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).