The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Akihiko Odaki <akihiko.odaki@daynix.com>,
	Baoquan He <bhe@redhat.com>, Dave Martin <Dave.Martin@arm.com>,
	Heiko Carstens <hca@linux.ibm.com>, Jan Kara <jack@suse.cz>,
	Kees Cook <kees@kernel.org>, kernel test robot <lkp@intel.com>,
	sunliming <sunliming@kylinos.cn>, Timur Tabi <ttabi@nvidia.com>,
	Yonatan Goldschmidt <yon.goldschmidt@gmail.com>
Subject: [GIT PULL] execve updates for v6.15-rc1
Date: Mon, 17 Mar 2025 09:12:08 -0700	[thread overview]
Message-ID: <202503170912.7B08D1FE19@keescook> (raw)

Hi Linus,

Please pull these execve updates for v6.15-rc1.

Thanks!

-Kees

The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:

  Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.15-rc1

for you to fetch changes up to 8d68cabeb1ff1cea57caae79a76a5606b11dbb4a:

  binfmt_elf_fdpic: fix variable set but not used warning (2025-03-07 20:07:33 -0800)

----------------------------------------------------------------
execve updates for v6.15-rc1

- elf: Define and use note name macros (Akihiko Odaki)

- elf: add remaining SHF_ flag macros (Timur Tabi)

- binfmt: Remove loader from linux_binprm struct (Yonatan Goldschmidt)

- binfmt_elf_fdpic: fix variable set but not used warning (sunliming)

----------------------------------------------------------------
Akihiko Odaki (6):
      elf: Define note name macros
      binfmt_elf: Use note name macros
      powerpc/crash: Use note name macros
      crash: Use note name macros
      s390/crash: Use note name macros
      crash: Remove KEXEC_CORE_NOTE_NAME

Timur Tabi (1):
      elf: add remaining SHF_ flag macros

Yonatan Goldschmidt (1):
      binfmt: Remove loader from linux_binprm struct

sunliming (1):
      binfmt_elf_fdpic: fix variable set but not used warning

 arch/powerpc/kernel/fadump.c               |  2 +-
 arch/powerpc/platforms/powernv/opal-core.c |  8 +--
 arch/s390/kernel/crash_dump.c              | 62 +++++++------------
 fs/binfmt_elf.c                            | 21 +++----
 fs/binfmt_elf_fdpic.c                      | 13 ++--
 fs/exec.c                                  |  2 -
 fs/proc/kcore.c                            | 12 ++--
 include/linux/binfmts.h                    |  2 +-
 include/linux/kexec.h                      |  2 -
 include/linux/vmcore_info.h                |  3 +-
 include/uapi/linux/elf.h                   | 99 ++++++++++++++++++++++++++++--
 kernel/crash_core.c                        |  2 +-
 12 files changed, 148 insertions(+), 80 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2025-03-17 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 16:12 Kees Cook [this message]
2025-03-25  0:45 ` [GIT PULL] execve updates for v6.15-rc1 pr-tracker-bot

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=202503170912.7B08D1FE19@keescook \
    --to=kees@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=bhe@redhat.com \
    --cc=hca@linux.ibm.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=sunliming@kylinos.cn \
    --cc=torvalds@linux-foundation.org \
    --cc=ttabi@nvidia.com \
    --cc=yon.goldschmidt@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