linux-kernel - Re: possible endless loop in PROM initialization

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] [day] [month] [year] [list]

Message-Id: <20070820201913.7a3e9009.krzysztof.h1@wp.pl>
Date:	Mon, 20 Aug 2007 20:19:13 +0200
From:	Krzysztof Helt <krzysztof.h1@...pl>
To:	Markus Dahms <mad@...omagically.de>
Cc:	David Miller <davem@...emloft.net>, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: possible endless loop in PROM initialization

On Mon, 20 Aug 2007 12:53:20 +0200
Markus Dahms <mad@...omagically.de> wrote:

> Hello again,

> As I'm not sure anymore whether the device tree (show-devs) or the aliases
> (devalias) are broken on the Classic X (I "upgraded" mine to a Classic by
> changing some NVRAM bytes) this may be a non-issue. But it is still an
> endless loop where it don't has to be.
> 

I understand your problem now. The only rational solution is
to stop building the list in the build_one_prop() if the property 
with already found name is defined.

Changing way the *_nextprop() works seems not a good 
idea to me.

My two cents,
Krzysztof
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/