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

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

Message-Id: <20080430163355.4b4f23ec.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Wed, 30 Apr 2008 16:33:55 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	David Miller <davem@...emloft.net>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	y-goto@...fujitsu.com
Subject: Re: sparc64 bootup regression...

On Wed, 30 Apr 2008 00:25:30 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
> Date: Wed, 30 Apr 2008 16:15:40 +0900
> 
> > How about this ? If this is messy (or doesn't work), Goto-san will rework
> > his own patch by himself. (this patch is against -mm but I think no HUNK to
> > git tree)
> 
> This makes the original change pointless.
> 
It seems the orignal change expects NODE_DATA() is allocated at boottime.
not in .bss section.

> If the goal is to put the usemap in the same section as the memory
> itself, in order to allow for it to be freed during memory hotplug,
> this new change just makes the facility not work some of the time.
> 
yes, at least, WARNING is necessary.

> Now maybe sometimes it will work, maybe sometimes it will not.
> 
> It's not the end of the world if this change is reverted for a few
> days while we work out what to do about this.
> 
yes ;)

> Really, it does not reflect badly upon you or Goto-san, if the change
> is reverted temporarily.
> 
Okay, I agree to revert it.

Thanks,
-Kame

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