From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40C86C43217 for ; Thu, 31 Mar 2022 07:11:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232040AbiCaHNm (ORCPT ); Thu, 31 Mar 2022 03:13:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39590 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231989AbiCaHNN (ORCPT ); Thu, 31 Mar 2022 03:13:13 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 8E9C144A38; Thu, 31 Mar 2022 00:11:20 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id E707F92009E; Thu, 31 Mar 2022 09:11:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id E08BE92009C; Thu, 31 Mar 2022 08:11:19 +0100 (BST) Date: Thu, 31 Mar 2022 08:11:19 +0100 (BST) From: "Maciej W. Rozycki" To: Bjorn Helgaas cc: Bjorn Helgaas , 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 In-Reply-To: Message-ID: References: <20220301231547.GA663097@bhelgaas> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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: Do you need any further information? Maciej