linux-kernel - Re: [PATCH] Revert "bus: ti-sysc: Probe for l4_wkup and l4

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <54d8461660c0910398b8bc5695f28446f8318ebd.camel@siemens.com>
Date: Wed, 19 Mar 2025 07:18:45 +0000
From: "Sverdlin, Alexander" <alexander.sverdlin@...mens.com>
To: "tony@...mide.com" <tony@...mide.com>, "andreas@...nade.info"
	<andreas@...nade.info>
CC: "rogerq@...nel.org" <rogerq@...nel.org>, "aaro.koskinen@....fi"
	<aaro.koskinen@....fi>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-omap@...r.kernel.org"
	<linux-omap@...r.kernel.org>, "khilman@...libre.com" <khilman@...libre.com>
Subject: Re: [PATCH] Revert "bus: ti-sysc: Probe for l4_wkup and l4_cfg
 interconnect devices first"

Hi Tony,

On Wed, 2025-03-19 at 05:56 +0200, Tony Lindgren wrote:
> > > > > This reverts commit 4700a00755fb5a4bb5109128297d6fd2d1272ee6.
> > > > > 
> > > > > It brakes target-module@...00050 ("ti,sysc-omap2") probe on AM62x in a case
> > > > > when minimally-configured system tries to network-boot:
> > > > >    
> > > > brakes or breaks? To unterstand the severity of the issue...  
> > > 
> > > Thanks for the correction, it should have been "breaks"...
> > > 
> > > > > [    6.888776] probe of 2b300050.target-module returned 517 after 258 usecs
> > > > > [   17.129637] probe of 2b300050.target-module returned 517 after 708 usecs
> > > > > [   17.137397] platform 2b300050.target-module: deferred probe pending: (reason unknown)
> > > > > [   26.878471] Waiting up to 100 more seconds for network.
> > > > > 
> > > > > Arbitrary 10 deferrals is really not a solution to any problem.  

...

> Reverting the commit does not really fix the root cause. It just ignores
> the problem of the hierarchy of the interconnect instances. Some of the
> interconnect instances are always-on, and contain devices providing
> resources for the other interconnect devices. So I would not consider
> patching MMC aliases all over the place as an alternative to fixing the
> real problem :)

I suppose you still have the test case which didn't work for you back then?
Because in this case I could help you with proper mmc aliases.

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com