linux-kernel - Re: [PATCH v2 08/14] objtool: Add elf_create

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210319153753.uhobpixww666c6op@treble>
Date:   Fri, 19 Mar 2021 10:37:53 -0500
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     x86@...nel.org, jgross@...e.com, mbenes@...e.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 08/14] objtool: Add elf_create_reloc() helper

On Fri, Mar 19, 2021 at 04:24:40PM +0100, Peter Zijlstra wrote:
> On Fri, Mar 19, 2021 at 10:12:59AM -0500, Josh Poimboeuf wrote:
> 
> > > -void elf_add_reloc(struct elf *elf, struct reloc *reloc)
> > > +int elf_add_reloc(struct elf *elf, struct section *sec, unsigned long offset,
> > > +		  unsigned int type, struct symbol *sym, int addend)
> > >  {
> > > -	struct section *sec = reloc->sec;
> > > +	struct reloc *reloc;
> > > +
> > > +	reloc = malloc(sizeof(*reloc));
> > > +	if (!reloc) {
> > > +		perror("malloc");
> > > +		return -1;
> > > +	}
> > > +	memset(reloc, 0, sizeof(*reloc));
> > > +
> > > +	reloc->sec = sec->reloc;
> > 
> > Maybe elf_add_reloc() could create the reloc section if it doesn't
> > already exist, that would help remove the multiple calls to
> > elf_create_reloc_section().
> 
> I'll do that as yet another patch ;-)

Ok!

> > > +	reloc->offset = offset;
> > > +	reloc->type = type;
> > > +	reloc->sym = sym;
> > > +	reloc->addend = addend;
> > >  
> > >  	list_add_tail(&reloc->list, &sec->reloc_list);
> > 
> > This should be sec->reloc->reloc_list?
> 
> Absolutely, there were a few other 'funnies' as well that I just fixed
> whilst trying to make the whole new stack work again :-)

I'm sure some of those were my fault, thanks for testing my crap :-)

-- 
Josh