From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: manual merge of the tip tree with the powerpc-objtool tree
Date: Fri, 16 Dec 2022 10:09:05 +1100 [thread overview]
Message-ID: <20221216100905.78f9ecd9@canb.auug.org.au> (raw)
In-Reply-To: <20221124122931.266df8c7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3295 bytes --]
Hi all,
On Thu, 24 Nov 2022 12:29:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> tools/objtool/check.c
>
> between commit:
>
> efb11fdb3e1a ("objtool: Fix SEGFAULT")
>
> from the powerpc-objtool tree and commit:
>
> dbcdbdfdf137 ("objtool: Rework instruction -> symbol mapping")
>
> from the tip tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc tools/objtool/check.c
> index 7580c66ca5c8,4f1a7384426b..000000000000
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@@ -207,7 -204,7 +204,7 @@@ static bool __dead_end_function(struct
> return false;
>
> insn = find_insn(file, func->sec, func->offset);
> - if (!insn || !insn->func)
> - if (!insn_func(insn))
> ++ if (!insn || !insn_func(insn))
> return false;
>
> func_for_each_insn(file, func, insn) {
> @@@ -850,11 -861,73 +861,73 @@@ static int create_ibt_endbr_seal_sectio
> return 0;
> }
>
> + static int create_cfi_sections(struct objtool_file *file)
> + {
> + struct section *sec, *s;
> + struct symbol *sym;
> + unsigned int *loc;
> + int idx;
> +
> + sec = find_section_by_name(file->elf, ".cfi_sites");
> + if (sec) {
> + INIT_LIST_HEAD(&file->call_list);
> + WARN("file already has .cfi_sites section, skipping");
> + return 0;
> + }
> +
> + idx = 0;
> + for_each_sec(file, s) {
> + if (!s->text)
> + continue;
> +
> + list_for_each_entry(sym, &s->symbol_list, list) {
> + if (sym->type != STT_FUNC)
> + continue;
> +
> + if (strncmp(sym->name, "__cfi_", 6))
> + continue;
> +
> + idx++;
> + }
> + }
> +
> + sec = elf_create_section(file->elf, ".cfi_sites", 0, sizeof(unsigned int), idx);
> + if (!sec)
> + return -1;
> +
> + idx = 0;
> + for_each_sec(file, s) {
> + if (!s->text)
> + continue;
> +
> + list_for_each_entry(sym, &s->symbol_list, list) {
> + if (sym->type != STT_FUNC)
> + continue;
> +
> + if (strncmp(sym->name, "__cfi_", 6))
> + continue;
> +
> + loc = (unsigned int *)sec->data->d_buf + idx;
> + memset(loc, 0, sizeof(unsigned int));
> +
> + if (elf_add_reloc_to_insn(file->elf, sec,
> + idx * sizeof(unsigned int),
> + R_X86_64_PC32,
> + s, sym->offset))
> + return -1;
> +
> + idx++;
> + }
> + }
> +
> + return 0;
> + }
> +
> static int create_mcount_loc_sections(struct objtool_file *file)
> {
> - struct section *sec;
> - unsigned long *loc;
> + int addrsize = elf_class_addrsize(file->elf);
> struct instruction *insn;
> + struct section *sec;
> int idx;
>
> sec = find_section_by_name(file->elf, "__mcount_loc");
This is now a conflict between the powerpc tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-12-15 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 1:29 linux-next: manual merge of the tip tree with the powerpc-objtool tree Stephen Rothwell
2022-11-24 6:58 ` Christophe Leroy
2022-11-24 10:37 ` Michael Ellerman
2022-12-15 23:09 ` Stephen Rothwell [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=20221216100905.78f9ecd9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).