linux-kernel - memblock updates

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-next>] [day] [month] [year] [list]

Message-Id: <1281071724-28740-1-git-send-email-benh@kernel.crashing.org>
Date:	Fri,  6 Aug 2010 15:14:41 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	linux-kernel@...r.kernel.org
Cc:	linux-mm@...ck.org, torvalds@...ux-foundation.org
Subject: memblock updates

Hi folks !

Here's my current branch. This time build tested on sparc(64), arm,
powerpc and sh. I don't have a microblaze compiler at hand.

Not much difference from the previous one. Off the top of my head:

 - Added the memblock_is_region_reserved() fix at the beginning
   (I'll send that to Linus separately if we decide this series
   shouldn't go in 2.6.36)
 - Split the patch adding the new accessors into separate patches
   for adding the accessors, converting each arch, and removing
   the old accessors. This makes it clearer, easier to review,
   etc... I added a couple new accessors for ARM.
 - Added the ARM updates based on what's upstream now (involves
   new memblock_is_memory() and memblock_is_memory_region() for
   use by ARM, nothing fancy there).

So very little changes. I haven't changed the init sections so
the warnings reported by Steven are still there. I will fix them
as an addon patch as I don't believe there's any actual breakage.

Now, what do you guys want to do with this now ? I can ask Linus
to pull now or we can wait until the end of the merge window and
put it into -next for another round...

Cheers,
Ben.

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