public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <kees@kernel•org>, Thomas Gleixner <tglx@linutronix•de>,
	Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
	Peter Zijlstra <peterz@infradead•org>
Cc: "Borislav Petkov (AMD)" <bp@alien8•de>,
	Jini Susan George <jinisusan.george@amd•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Roman Kisel <romank@linux•microsoft.com>,
	Vignesh Balasubramanian <vigbalas@amd•com>
Subject: linux-next: manual merge of the execve tree with the tip tree
Date: Wed, 7 Aug 2024 13:14:05 +1000	[thread overview]
Message-ID: <20240807131405.10e3665d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

Hi all,

Today's linux-next merge of the execve tree got a conflict in:

  fs/binfmt_elf.c

between commit:

  ba386777a30b ("x86/elf: Add a new FPU buffer layout info to x86 core files")

from the tip tree and commit:

  fb97d2eb542f ("binfmt_elf, coredump: Log the reason of the failed core dumps")

from the execve 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 fs/binfmt_elf.c
index 01bcbe7fdebd,bf9bfd1a0007..000000000000
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@@ -2092,20 -2102,28 +2102,28 @@@ static int elf_core_dump(struct coredum
  			phdr.p_flags |= PF_X;
  		phdr.p_align = ELF_EXEC_PAGESIZE;
  
- 		if (!dump_emit(cprm, &phdr, sizeof(phdr)))
+ 		if (!dump_emit(cprm, &phdr, sizeof(phdr))) {
+ 			coredump_report_failure("Error emitting program headers");
  			goto end_coredump;
+ 		}
  	}
  
- 	if (!elf_core_write_extra_phdrs(cprm, offset))
+ 	if (!elf_core_write_extra_phdrs(cprm, offset)) {
+ 		coredump_report_failure("Error writing out extra program headers");
  		goto end_coredump;
+ 	}
  
  	/* write out the notes section */
- 	if (!write_note_info(&info, cprm))
+ 	if (!write_note_info(&info, cprm)) {
+ 		coredump_report_failure("Error writing out notes");
  		goto end_coredump;
+ 	}
  
 -	/* For cell spufs */
 +	/* For cell spufs and x86 xstate */
- 	if (elf_coredump_extra_notes_write(cprm))
+ 	if (elf_coredump_extra_notes_write(cprm)) {
+ 		coredump_report_failure("Error writing out extra notes");
  		goto end_coredump;
+ 	}
  
  	/* Align to page */
  	dump_skip_to(cprm, dataoff);

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2024-08-07  3:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240807131405.10e3665d@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bp@alien8$(echo .)de \
    --cc=hpa@zytor$(echo .)com \
    --cc=jinisusan.george@amd$(echo .)com \
    --cc=kees@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@redhat$(echo .)com \
    --cc=peterz@infradead$(echo .)org \
    --cc=romank@linux$(echo .)microsoft.com \
    --cc=tglx@linutronix$(echo .)de \
    --cc=vigbalas@amd$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox