linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Eric Biederman <ebiederm@xmission.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Brown <broonie@kernel.org>,
	Dave Martin <Dave.Martin@arm.com>, Baoquan He <bhe@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
	LEROY Christophe <christophe.leroy2@cs-soprasteria.com>,
	Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Kees Cook <kees@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	kexec@lists.infradead.org, binutils@sourceware.org,
	devel@daynix.com, Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [PATCH v5 0/6] elf: Define note name macros
Date: Mon, 10 Feb 2025 16:58:30 -0800	[thread overview]
Message-ID: <173923550723.2947986.17868728802985188618.b4-ty@kernel.org> (raw)
In-Reply-To: <20250115-elf-v5-0-0f9e55bbb2fc@daynix.com>

On Wed, 15 Jan 2025 14:47:57 +0900, Akihiko Odaki wrote:
> elf.h had a comment saying:
> > Notes used in ET_CORE. Architectures export some of the arch register
> > sets using the corresponding note types via the PTRACE_GETREGSET and
> > PTRACE_SETREGSET requests.
> > The note name for these types is "LINUX", except NT_PRFPREG that is
> > named "CORE".
> 
> [...]

I rebased this for changes introduced by commit
680e029fd62f ("proc/kcore: don't walk list on every read")

Applied to for-next/execve, thanks!

[1/6] elf: Define note name macros
      https://git.kernel.org/kees/c/7da8e4ad4df0
[2/6] binfmt_elf: Use note name macros
      https://git.kernel.org/kees/c/2fc4947bbd91
[3/6] powerpc: Use note name macros
      https://git.kernel.org/kees/c/609c8b309156
[4/6] crash: Use note name macros
      https://git.kernel.org/kees/c/0de47f28ec84
[5/6] s390/crash: Use note name macros
      https://git.kernel.org/kees/c/d4a760fb77fd
[6/6] crash: Remove KEXEC_CORE_NOTE_NAME
      https://git.kernel.org/kees/c/7e620b56d958

Take care,

-- 
Kees Cook



      parent reply	other threads:[~2025-02-11  0:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15  5:47 Akihiko Odaki
2025-01-15  5:47 ` [PATCH v5 1/6] " Akihiko Odaki
2025-01-15 17:11   ` Dave Martin
2025-01-15  5:47 ` [PATCH v5 2/6] binfmt_elf: Use " Akihiko Odaki
2025-01-15  5:48 ` [PATCH v5 3/6] powerpc: " Akihiko Odaki
2025-01-15  5:48 ` [PATCH v5 4/6] crash: " Akihiko Odaki
2025-01-15  5:48 ` [PATCH v5 5/6] s390/crash: " Akihiko Odaki
2025-01-15  5:48 ` [PATCH v5 6/6] crash: Remove KEXEC_CORE_NOTE_NAME Akihiko Odaki
2025-02-11  0:58 ` Kees Cook [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=173923550723.2947986.17868728802985188618.b4-ty@kernel.org \
    --to=kees@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=bhe@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.leroy2@cs-soprasteria.com \
    --cc=devel@daynix.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hca@linux.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=vgoyal@redhat.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