mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Michael Forney <mforney@mforney.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] objtool: Check for gelf_update_rel[a] failures
Date: Mon, 28 Jun 2021 10:24:38 +0200	[thread overview]
Message-ID: <YNmHRi+00RAAUmEt@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAGw6cBv2NBCDrZb7ZnmAhZOJ_EwgW6tR-8AfY2v=T9OkD=6O8g@mail.gmail.com>

On Mon, Jun 28, 2021 at 12:52:07AM -0700, Michael Forney wrote:
> On 2021-05-08, Michael Forney <mforney@mforney.org> wrote:
> > Otherwise, if these fail we end up with garbage data in the
> > .rela.orc_unwind_ip section, leading to errors like
> >
> >   ld: fs/squashfs/namei.o: bad reloc symbol index (0x7f16 >= 0x12) for
> > offset 0x7f16d5c82cc8 in section `.orc_unwind_ip'
> >
> > Signed-off-by: Michael Forney <mforney@mforney.org>
> 
> Ping on these patches.

Josh, I forever forget which libelf versions we're supposed to support,

But these patches do look reasonable to me, wdyt?

  reply	other threads:[~2021-06-28  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09  0:01 Michael Forney
2021-05-09  0:01 ` [PATCH 2/2] objtool: Update section header before relocations Michael Forney
2021-06-29  7:55   ` Miroslav Benes
2021-10-13 21:42   ` [tip: objtool/urgent] " tip-bot2 for Michael Forney
2021-06-28  7:52 ` [PATCH 1/2] objtool: Check for gelf_update_rel[a] failures Michael Forney
2021-06-28  8:24   ` Peter Zijlstra [this message]
2021-06-29 17:12     ` Josh Poimboeuf
2021-08-28 19:04       ` Michael Forney
2021-10-06 16:58         ` Michael Forney
2021-10-07  3:16           ` Josh Poimboeuf
2021-06-29  7:54 ` Miroslav Benes
2021-10-13 21:42 ` [tip: objtool/urgent] " tip-bot2 for Michael Forney

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=YNmHRi+00RAAUmEt@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mforney@mforney.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

all inboxes | Powered by JetHome®