linux-kernel - Re: [PATCH 1/2] PCI: Setup bridge resources earlier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3d626c68-8e63-7e5b-a08a-c47845ee06eb@linux.intel.com>
Date: Mon, 27 Oct 2025 15:49:14 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Bhanu Seshu Kumar Valluri <bhanuseshukumar@...il.com>
cc: Bjorn Helgaas <helgaas@...nel.org>, bhelgaas@...gle.com, kw@...ux.com, 
    LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org, 
    lucas.demarchi@...el.com, rafael.j.wysocki@...el.com, 
    Manivannan Sadhasivam <mani@...nel.org>
Subject: Re: [PATCH 1/2] PCI: Setup bridge resources earlier

On Mon, 27 Oct 2025, Bhanu Seshu Kumar Valluri wrote:
> On 21/10/25 00:16, Ilpo Järvinen wrote:
> > On Sat, 18 Oct 2025, Bhanu Seshu Kumar Valluri wrote:
> > 
> >> On 18/10/25 00:22, Bjorn Helgaas wrote:
> >>> On Fri, Oct 17, 2025 at 11:52:58PM +0530, Bhanu Seshu Kumar Valluri wrote:
> >>>>
> >>>> I want to report that this PATCH also break PCI RC port on TI-AM64-EVM.
> >>>>
> >>>> I did git bisect and it pointed to the a43ac325c7cb ("PCI: Set up bridge resources earlier")
> >>>>
> >>>> Happy to help if any testing or logs are required.
> >>>
> >>> Thanks for the report!  Can you test this patch?
> >>>
> >>>   https://patch.msgid.link/20251014163602.17138-1-ilpo.jarvinen@linux.intel.com
> >>>
> >>> That patch is queued up as
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?id=469276c06aff
> >>> and should appear in v6.18-rc2 on Sunday if all goes well.
> >>>
> >>> If that doesn't work, let us know and we'll debug this further.
> >>
> >> I applied above patch on top of commit f406055cb18c ("Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux")
> >>
> >> Did pci rescan and run kselftest (pci_endpoint_test). It is working.
> >>
> >> Thanks for the patch.
> > 
> > Thanks for testing the revert.
> > 
> >> Happy to help if any testing or logs are required.
> > 
> > I'd be interested to understand what goes wrong with the change I was 
> > trying to make as I want to attempt the same change later, but with all 
> > known issues solved by supporting changes, obviously :-).
> > 
> > The log snippets you provided are unfortunately too short to contain all 
> > the necessary information (missing e.g. root bus resources and possibly 
> > other helpful details).
> > 
> > So if you could provide dmesg and /proc/iomem contents from broken and
> > working (with the revert) cases to let me easily compare them, that would 
> > help. Please take the dmesg with dyndbg="file drivers/pci/*.c +p" on 
> > kernel's cmdline.
> > 
> > No further actions needed beyond that until later if I need to test some 
> > of those supporting changes before retrying all this in the mainline. It 
> > may take some time, even more than one kernel cycle as there have been 
> > quite many regressions.
> > 
> > 
> Hi
> 
> I captured logs with dyndbg="file drivers/pci/*.c +p. See the links below.
> 
> Working kernel logs
> https://github.com/bhanuseshukumar/kernel_logs/blob/main/working_log
> 
> Non Working kernel logs
> https://github.com/bhanuseshukumar/kernel_logs/blob/main/not_working_log
> 
> Happy to help if any testing or logs are required.

Could you try if booting with pci=realloc helps? (It might be that it is 
ineffective like I saw in some other case.)

And also test if this old size removal patch helps:

https://lore.kernel.org/linux-pci/922b1f68-a6a2-269b-880c-d594f9ca6bde@linux.intel.com/


-- 
 i.