LKML Archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Allen Pais <apais@linux.microsoft.com>,
	Jini Susan George <jinisusan.george@amd.com>,
	Kees Cook <keescook@chromium.org>, Marco Elver <elver@google.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Steven Rostedt <rostedt@goodmis.org>,
	Vignesh Balasubramanian <vigbalas@amd.com>,
	Vijay Nag <nagvijay@microsoft.com>,
	y0un9n132@gmail.com
Subject: [GIT PULL] execve updates for 6.10-rc1
Date: Sat, 11 May 2024 12:24:23 -0700	[thread overview]
Message-ID: <202405111224.433C7AEAB@keescook> (raw)

Hi Linus,

Please pull this handful of execve updates for 6.10-rc1.

Thanks!

-Kees

The following changes since commit 39cd87c4eb2b893354f3b850f916353f2658ae6f:

  Linux 6.9-rc2 (2024-03-31 14:32:39 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 4bbf9c3b53e637eb3a14ee27b996300ce88e752a:

  fs/coredump: Enable dynamic configuration of max file note size (2024-05-08 09:53:00 -0700)

----------------------------------------------------------------
execve updates for 6.10-rc1

- Provide knob to change (previously fixed) coredump NOTES size (Allen Pais)

- Add sched_prepare_exec tracepoint (Marco Elver)

- Make /proc/$pid/auxv work under binfmt_elf_fdpic (Max Filippov)

- Convert ARCH_HAVE_EXTRA_ELF_NOTES to proper Kconfig (Vignesh Balasubramanian)

- Leave a gap between .bss and brk

----------------------------------------------------------------
Allen Pais (1):
      fs/coredump: Enable dynamic configuration of max file note size

Kees Cook (1):
      binfmt_elf: Leave a gap between .bss and brk

Marco Elver (1):
      tracing: Add sched_prepare_exec tracepoint

Max Filippov (1):
      binfmt_elf_fdpic: fix /proc/<pid>/auxv

Vignesh Balasubramanian (1):
      Replace macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig

 arch/Kconfig                   |  9 +++++
 arch/powerpc/Kconfig           |  1 +
 arch/powerpc/include/asm/elf.h |  2 -
 fs/binfmt_elf.c                | 10 ++++-
 fs/binfmt_elf_fdpic.c          | 85 +++++++++++++++++++-----------------------
 fs/coredump.c                  | 17 +++++++++
 fs/exec.c                      |  8 ++++
 include/linux/coredump.h       |  2 +
 include/linux/elf.h            |  2 +-
 include/trace/events/sched.h   | 35 +++++++++++++++++
 10 files changed, 120 insertions(+), 51 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2024-05-11 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 19:24 Kees Cook [this message]
2024-05-13 21:33 ` [GIT PULL] execve updates for 6.10-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=202405111224.433C7AEAB@keescook \
    --to=keescook@chromium.org \
    --cc=apais@linux.microsoft.com \
    --cc=elver@google.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jinisusan.george@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=nagvijay@microsoft.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vigbalas@amd.com \
    --cc=y0un9n132@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).