From: Vivek Goyal <vgoyal@in.ibm.com>
To: Simon Horman <horms@verge.net.au>
Cc: fastboot@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kdump/kexec: calculate note size at compile time
Date: Wed, 28 Mar 2007 12:13:53 +0530 [thread overview]
Message-ID: <20070328064353.GD4941@in.ibm.com> (raw)
In-Reply-To: <20070328061855.GA9576@verge.net.au>
On Wed, Mar 28, 2007 at 03:18:58PM +0900, Simon Horman wrote:
> Currently the size of the per-cpu region reserved to save crash
> notes is set by the per-architecture value MAX_NOTE_BYTES. Which
> in turn is currently set to 1024 on all supported architectures.
>
> While testing ia64 I recently discovered that this value is
> in fact too small. The particular setup I was using actually
> needs 1172 bytes. This lead to very tedious failure mode
> where the tail of one elf note would overwrite the head of
> another if they ended up being alocated sequentially by kmalloc,
> which was often the case.
>
> It seems to me that a far better approach is to caclculate the size
> that the area needs to be. This patch does just that.
>
> If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
> is needed then this should be as easy as making MAX_NOTE_BYTES
> larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
> However, I think that the approach in this patch is a much more robust idea.
>
Makes sense to me. Calculating the size based on elf_prstatus is better
than hardcoding it to some value.
A minor query is inlined below.
[..]
> ===================================================================
> --- linux-2.6.orig/include/linux/kexec.h 2007-03-28 09:42:14.000000000 +0900
> +++ linux-2.6/include/linux/kexec.h 2007-03-28 12:32:50.000000000 +0900
> @@ -7,6 +7,8 @@
> #include <linux/linkage.h>
> #include <linux/compat.h>
> #include <linux/ioport.h>
> +#include <linux/elfcore.h>
> +#include <linux/elf.h>
> #include <asm/kexec.h>
>
> /* Verify architecture specific macros are defined */
> @@ -31,6 +33,13 @@
> #error KEXEC_ARCH not defined
> #endif
>
> +#define KEXEC_NOTE_NAME "CORE"
> +#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
> +#define KEXEC_NOTE_NAME_BYTES ALIGN(strlen(KEXEC_NOTE_NAME) + 1, 4)
> +#define KEXEC_NOTE_BODY_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
> +#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
Why are we multiplying KEXEC_NOTE_HEAD_BYTES with 2?
Thanks
Vivek
next prev parent reply other threads:[~2007-03-28 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 6:18 Simon Horman
2007-03-28 6:43 ` Vivek Goyal [this message]
2007-03-28 7:13 ` Horms
2007-03-28 8:08 ` Vivek Goyal
2007-03-29 3:30 ` Simon Horman
2007-03-29 3:44 ` Vivek Goyal
2007-03-29 3:48 ` Simon Horman
2007-03-30 0:41 ` Andrew Morton
2007-03-30 2:34 ` Simon Horman
2007-04-02 4:48 ` Simon Horman
2007-04-02 10:10 ` Simon Horman
2007-04-03 9:37 Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070328064353.GD4941@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=fastboot@lists.linux-foundation.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome