mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Krzysztof Halasa" <khc@pm.waw.pl>, Alan <alan@clueserver.org>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Additional info on modpost segfault
Date: Sat, 12 Jun 2010 00:49:47 +0200	[thread overview]
Message-ID: <20100611224947.GA17453@sepie.suse.cz> (raw)
In-Reply-To: <4C129FC7.8070308@zytor.com>

On Fri, Jun 11, 2010 at 01:42:47PM -0700, H. Peter Anvin wrote:
> Michal, are you sending this to Linus?

I'll, once Linus takes another pull request I sent a couple of hours
ago. Thanks for the patch Krzysztof!

Michal

> 
> 	-hpa
> 
> 
> On 06/10/2010 04:08 PM, Krzysztof Halasa wrote:
> > 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)
> > --
> > 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/
> 
> --
> 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/

      reply	other threads:[~2010-06-11 22:49 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
2010-06-11  0:06         ` alan
2010-06-11 20:42         ` H. Peter Anvin
2010-06-11 22:49           ` Michal Marek [this message]

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=20100611224947.GA17453@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=alan@clueserver.org \
    --cc=hpa@zytor.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --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®