linux-kernel - Re: [git pull] "big box" x86 changes, bootmem/sparsemem

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:	Mon, 28 Apr 2008 18:58:14 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Siddha\, Suresh B" <suresh.b.siddha@...el.com>
Subject: Re: [git pull] "big box" x86 changes, bootmem/sparsemem

Hi,

"Yinghai Lu" <yhlu.kernel@...il.com> writes:

> On Sun, Apr 27, 2008 at 3:48 PM, Johannes Weiner <hannes@...urebad.de> wrote:
>> Hi Ingo,
>>
>>
>>  Ingo Molnar <mingo@...e.hu> writes:
>>
>>  > * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>  >
>>  >> IOW, they'd be big enough that people hopefully don't start nitpicking
>>  >> about some *totally* uninteresting small detail, but small enough that
>>  >> people can read it through without losing concentration about a
>>  >> quarter of the way in.
>>  >
>>  > ok. Here's the "memory management" type of changes:
>>  >
>>  >    git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86-bigbox-bootmem.git for-linus
>>  >
>>  > the other sub-trees will depend on these changes. I think these
>>  > infrastructure and other improvements are mergable and pullable as-is.
>>  >
>>  >       Ingo
>>  >
>>  > ------------------>
>>
>>  [...]
>>
>>
>>  >       mm: allow reserve_bootmem() cross nodes
>>
>>  I find it sad that this goes in now.  I wrote a clean version of
>>  reserve_bootmem() [1] and it was rejected with arguments that I did not
>>  understand [2] and that were not further explained even though I asked
>>  for it [3].
>>
>>  http://lkml.org/lkml/2008/4/16/76
>>  http://lkml.org/lkml/2008/4/16/234
>>  http://lkml.org/lkml/2008/4/16/250
>>
>>  Your comment was rather unfair, because it gave the impression you did
>>  not read the thread before replying.  And you did not react to other
>>  explicit questions from me.  If you find my patches to be crap, say so
>>  and please explain WHY so I have a chance to improve.
>
> this thread is for reserve_bootmem ?

Sorry, my mistake.  I was referring to

5a982cbc7b3fe6cf72266f319286f29963c71b9e: mm: fix boundary checking in
free_bootmem_core

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