mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Alan <alan@clueserver.org>
Cc: "Michal Marek" <mmarek@suse.cz>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Additional info on modpost segfault
Date: Fri, 11 Jun 2010 01:08:20 +0200	[thread overview]
Message-ID: <m37hm6zdsr.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1275929979.2923.0.camel@zowie.clueserver.org> (alan@clueserver.org's message of "Mon, 07 Jun 2010 09:59:39 -0700")

Alan <alan@clueserver.org> writes:

> program: /home/alan/GitTrees/linux-2.6-mid-ref/scripts/mod/modpost -o
> Module.symvers -S vmlinux.o
>
> Program received signal SIGSEGV, Segmentation fault.

It just hit me.
It's the offset calculation in reloc_location() which overflows:
        return (void *)elf->hdr + sechdrs[section].sh_offset +
               (r->r_offset - sechdrs[section].sh_addr);

E.g. for the first rodata r entry:
r->r_offset < sechdrs[section].sh_addr
and the expression in the parenthesis produces 0xFFFFFFE0 or something
equally wise.

Does the attached patch fix it?

Signed-off-by: Krzysztof Hałasa <khc@pm.waw.pl>

--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -1317,8 +1317,8 @@ static unsigned int *reloc_location(struct elf_info *elf,
 	Elf_Shdr *sechdrs = elf->sechdrs;
 	int section = sechdr->sh_info;
 
 	return (void *)elf->hdr + sechdrs[section].sh_offset +
-		(r->r_offset - sechdrs[section].sh_addr);
+		r->r_offset - sechdrs[section].sh_addr;
 }
 
 static int addend_386_rel(struct elf_info *elf, Elf_Shdr *sechdr, Elf_Rela *r)

  parent reply	other threads:[~2010-06-10 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  3:10 alan
2010-06-04  4:51 ` Américo Wang
2010-06-04  7:22   ` Michal Marek
2010-06-07 16:59     ` Alan
2010-06-08  5:51       ` Américo Wang
2010-06-08 18:24         ` Alan
2010-06-09  8:35           ` Américo Wang
2010-06-10 23:08       ` Krzysztof Halasa [this message]
2010-06-11  0:06         ` alan
2010-06-11 20:42         ` H. Peter Anvin
2010-06-11 22:49           ` Michal Marek

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=m37hm6zdsr.fsf@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --cc=alan@clueserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=xiyou.wangcong@gmail.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

all inboxes | Powered by JetHome®