| 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
| ||
|
Message-ID: <20080623152122.106a059c@kopernikus.site> Date: Mon, 23 Jun 2008 15:21:22 +0200 From: Bernhard Walle <bwalle@...e.de> To: Ingo Molnar <mingo@...e.hu> Cc: linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [patch 4/5] x86: use BOOTMEM_EXCLUSIVE on 32-bit * Ingo Molnar <mingo@...e.hu> [2008-06-23 12:53]: > > > [1] 62b5ebe062c2801f6d40480ae3b91a64c8c8e6cb > > but note that this too has dependencies, it relies on: > > # tip/x86/numa: ddeb8ef: x86: add flags parameter to reserve_bootmem_generic() > # tip/x86/numa: 62b5ebe: x86: use reserve_bootmem_generic() to reserve crashkernel memory on x86_64 The 2nd is not the dependency but the commit itself. > so i've initially delayed the whole topic to v2.6.27. Ok, you have more experience which patches should go into 2.6.26 at that point of time, so it's acceptable for me. > I've attached both patches below - are they really urgent enough to be > propagated to tip/x86/urgent and be sent to Linus? AFAICS these are > ancient issues with kernel crashdumping. I only brought up that topic again because it's a regression between 2.6.22 and 2.6.23 caused by 5c3391f9f749023a49c64d607da4fb49263690eb. Bernhard -- Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development -- 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/
Powered by blists - more mailing lists