From: Dave Young <dyoung@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Simon Horman <horms@verge.net.au>,
Kexec Mailing List <kexec@lists.infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH][V2] vmcore-dmesg: Determine correct machine pointer size
Date: Wed, 14 Nov 2012 15:38:43 +0800 [thread overview]
Message-ID: <50A34A83.1030901@redhat.com> (raw)
In-Reply-To: <20121113163827.GB12529@redhat.com>
On 11/14/2012 12:38 AM, Vivek Goyal wrote:
> A 32bit arch can prepare ELF64 headers. For example for PAE case to
> preresent file offsets 64bit but data size at the offset still remains
> 32bit. If we just base our decision based on EI_CLASS, then we will try
> to read 64bit data from file and can run into various issues.
>
> We ran into following issue when we tried to run vmcore-dmesg on a 32bit
> PAE system vmcore which had 64bit elf headers.
>
> No program header covering vaddr 0xc0a6a688c0b89100found kexec bug?
>
> Basically we try to read value of log_buf variable from address
> log_buf_vaddr. We read in 64bit value and then pass that value again
> to vaddr_to_offset() in an attempt to get to actual log_buf start
> and get error message.
>
> So determine the machine pointer size based on ELF class and arch and read
> the bytes from file accordingly.
>
> v2: Fixed the code as per suggestion from Eric.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Ack
> ---
> vmcore-dmesg/vmcore-dmesg.c | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> Index: kexec-tools/vmcore-dmesg/vmcore-dmesg.c
> ===================================================================
> --- kexec-tools.orig/vmcore-dmesg/vmcore-dmesg.c 2012-08-01 13:27:09.304878654 -0400
> +++ kexec-tools/vmcore-dmesg/vmcore-dmesg.c 2012-11-13 11:32:33.184358230 -0500
> @@ -89,6 +89,24 @@ static uint64_t vaddr_to_offset(uint64_t
> exit(30);
> }
>
> +static unsigned machine_pointer_bits(void)
> +{
> + uint8_t bits = 0;
> +
> + /* Default to the size of the elf class */
> + switch(ehdr.e_ident[EI_CLASS]) {
> + case ELFCLASS32: bits = 32; break;
> + case ELFCLASS64: bits = 64; break;
> + }
> +
> + /* Report the architectures pointer size */
> + switch(ehdr.e_machine) {
> + case EM_386: bits = 32; break;
> + }
> +
> + return bits;
> +}
> +
> static void read_elf32(int fd)
> {
> Elf32_Ehdr ehdr32;
> @@ -389,7 +407,8 @@ static uint64_t read_file_pointer(int fd
> {
> uint64_t result;
> ssize_t ret;
> - if (ehdr.e_ident[EI_CLASS] == ELFCLASS64) {
> +
> + if (machine_pointer_bits() == 64) {
> uint64_t scratch;
> ret = pread(fd, &scratch, sizeof(scratch), addr);
> if (ret != sizeof(scratch)) {
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-11-14 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 16:38 [PATCH][V2] vmcore-dmesg: Determine correct machine pointer size Vivek Goyal
2012-11-14 4:13 ` Eric W. Biederman
2012-11-14 7:38 ` Dave Young [this message]
2012-11-14 23:19 ` 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=50A34A83.1030901@redhat.com \
--to=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
/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