linux-kernel - Re: [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix

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]

Date:	Wed, 2 Aug 2006 23:38:02 -0700
From:	Andrew Morton <akpm@...l.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org, lhms-devel@...ts.sourceforge.net,
	kmannth@...ibm.com, y-goto@...fujitsu.com
Subject: Re: [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd
 handling fix

On Thu, 3 Aug 2006 12:30:39 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:

> After Keith's report of memory hotadd failure, I increased test patterns.
> These patches are a result of new patterns. But I cannot cover all existing
> memory layout in the world, more tests are needed.
> Now, I think my patch can make things better and want this codes to be tested
> in -mm.patche series is consitsts of 5 patches.

I expect the code which these patches touch is completely untested in -mm, so
all we'll get is compile testing and some review.

Given that these patches touch pretty much nothing but the memory hot-add
paths I'd be inclined to fast-track them into 2.6.18.  Do you agree that
these patches are sufficiently safe and that the problems that they solve
are sufficiently serious for us to take that approach?

Either way, could I ask that interested parties review this work closely
and promptly?

Thanks.

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