linux-kernel - Re: sparc64 bootup regression...

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]

Date:	Tue, 03 Jun 2008 15:14:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	y-goto@...fujitsu.com
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	kamezawa.hiroyu@...fujitsu.com
Subject: Re: sparc64 bootup regression...

From: Yasunori Goto <y-goto@...fujitsu.com>
Date: Wed, 30 Apr 2008 21:53:18 +0900

> I'll reconsider around here.

I think I know at least one of the problems in this change.

This code assumes that it can take __pa() on NODE_DATA().

But, if NUMA is disabled, NODE_DATA() is &contig_page_data which is a
kernel image symbol.  __pa() is not supported for such addresses.

It happens to work on x86, but it will not work on just about every
other platform.

There are several things to consider to fix this changeset and
get it back into a state where it can be resubmitted into the
tree:

1) What is the goal here wrt. allocating the usemap when NUMA
   is disabled.

2) What is appropriate if section_nr targetted allocation of
   the usemap fails.

It seems to me that the pgdat and usemap should be allocated
together if putting them into the same section is important.
This allows us to avoid case #2 completely, and therefore we
don't even need to consider how to handle such a failure.
--
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/