public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: linux-kernel@vger.kernel.org, Emanuele Rocca <emanuele.rocca@arm.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Jann Horn <jannh@google.com>, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v4 0/2] pidfds: add coredump_code field to pidfd_info
Date: Thu, 26 Mar 2026 15:42:47 +0100	[thread overview]
Message-ID: <20260326-spuken-synergie-b606ef9a6e49@brauner> (raw)
In-Reply-To: <acE5fYOgyVUYahIn@NH27D9T0LF>

On Mon, 23 Mar 2026 14:00:45 +0100, Emanuele Rocca wrote:
> This patchs series adds a new field called coredump_code to struct pidfd_info,
> as well as the relevant selftests. Note that the coredump selftests are
> currently not passing, and the following patch is needed to fix them:
> https://lore.kernel.org/lkml/ab2kI0PI_Vk6bU88@NH27D9T0LF/
> I have not included it in this series as it is not directly related to the
> coredump_code changes.
> 
> [...]

Applied to the vfs-7.1.pidfs branch of the vfs/vfs.git tree.
Patches in the vfs-7.1.pidfs branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.1.pidfs

[1/2] pidfds: add coredump_code field to pidfd_info
      https://git.kernel.org/vfs/vfs/c/701f7f4fbabb
[2/2] selftests: check pidfd_info->coredump_code correctness
      https://git.kernel.org/vfs/vfs/c/7aaa4915cb69

      parent reply	other threads:[~2026-03-26 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 13:00 [PATCH v4 0/2] pidfds: add coredump_code field to pidfd_info Emanuele Rocca
2026-03-23 13:02 ` [PATCH v5 1/2] " Emanuele Rocca
2026-03-23 13:03 ` [PATCH v5 2/2] selftests: check pidfd_info->coredump_code correctness Emanuele Rocca
2026-03-26 14:42 ` Christian Brauner [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=20260326-spuken-synergie-b606ef9a6e49@brauner \
    --to=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=emanuele.rocca@arm.com \
    --cc=jack@suse.cz \
    --cc=jannh@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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