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 for Android: free password hash cracker in your pocket

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

Message-Id: <20070820.010622.41634915.davem@davemloft.net>
Date:	Mon, 20 Aug 2007 01:06:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mad@...omagically.de
Cc:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: possible endless loop in PROM initialization

From: Markus Dahms <mad@...omagically.de>
Date: Mon, 20 Aug 2007 09:59:49 +0200

> I could track down the issue to the function __prom_nextprop() in
> arch/sparc/prom/tree.c, but I am now looking for the definition of
> prom_nodeops->no_nextprop() without success.

When we boot the firmware provides a vector of function
pointers, and this is prom_nodeops.  So prom_nodeops->no_nextprop()
is a routine inside the PROM.

-
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/