Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932946AbXJRLQ3 (ORCPT ); Thu, 18 Oct 2007 07:16:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763380AbXJRLPm (ORCPT ); Thu, 18 Oct 2007 07:15:42 -0400 Received: from ns2.suse.de ([195.135.220.15]:60731 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763325AbXJRLPl (ORCPT ); Thu, 18 Oct 2007 07:15:41 -0400 Message-Id: <20071018111535.356215664@strauss.suse.de> User-Agent: quilt/0.46-60 Date: Thu, 18 Oct 2007 13:15:35 +0200 From: Bernhard Walle To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org Cc: akpm@linux-foundation.org, ak@suse.de, vgoyal@in.ibm.com Subject: [patch 0/3] Protect crashkernel against BSS overlap Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2157 Lines: 49 I observed the problem that even when you choose the default 16M as crashkernel base address and the kernel is very big, the reserved area may overlap with the kernel BSS. Currently, this is not checked at runtime, so the kernel just crashes when you load the panic kernel in the sys_kexec call. This three patches check this at runtime. The patches are against current git, but with the patches extended-crashkernel-command-line.patch extended-crashkernel-command-line-update.patch extended-crashkernel-command-line-comment-fix.patch extended-crashkernel-command-line-improve-error-handling-in-parse_crashkernel_mem.patch use-extended-crashkernel-command-line-on-i386.patch use-extended-crashkernel-command-line-on-i386-update.patch use-extended-crashkernel-command-line-on-x86_64.patch use-extended-crashkernel-command-line-on-x86_64-update.patch use-extended-crashkernel-command-line-on-ia64.patch use-extended-crashkernel-command-line-on-ia64-fix.patch use-extended-crashkernel-command-line-on-ia64-update.patch use-extended-crashkernel-command-line-on-ppc64.patch use-extended-crashkernel-command-line-on-ppc64-update.patch use-extended-crashkernel-command-line-on-sh.patch use-extended-crashkernel-command-line-on-sh-update.patch from -mm tree applied since they are marked to be merged in 2.6.24. I know that the implementation of both patches is only x86 (i386 and x86-64), but if you agree that it's the way to go, I'll modify the patch for all architectures. Changes compared to last submit: 1) use BOOTMEM_DEFAULT instead of 0 to improve code readability (suggested by Dave Hansen ) 2) unreserve memory that got reserved until we detect a duplicate reservation (discovered by Vivek Goyal ) 3) fix IA64 (didn't compile) Signed-off-by: Bernhard Walle -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/