[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251102170353.GA3837@redhat.com>
Date: Sun, 2 Nov 2025 18:03:54 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Christian Brauner <brauner@...nel.org>
Cc: linux-fsdevel@...r.kernel.org, Amir Goldstein <amir73il@...il.com>,
Aleksa Sarai <cyphar@...har.com>,
Yu Watanabe <watanabe.yu+github@...il.com>,
Josef Bacik <josef@...icpanda.com>,
Jeff Layton <jlayton@...nel.org>, Jann Horn <jannh@...gle.com>,
Luca Boccassi <luca.boccassi@...il.com>,
Alexander Mikhalitsyn <alexander@...alicyn.com>,
linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>,
Lennart Poettering <lennart@...ttering.net>,
Mike Yuan <me@...dnzj.com>,
Zbigniew Jędrzejewski-Szmek <zbyszek@...waw.pl>
Subject: Re: [PATCH 00/22] coredump: cleanups & pidfd extension
On 10/28, Christian Brauner wrote:
>
> Christian Brauner (22):
> pidfs: use guard() for task_lock
> pidfs: fix PIDFD_INFO_COREDUMP handling
> pidfs: add missing PIDFD_INFO_SIZE_VER1
> pidfs: add missing BUILD_BUG_ON() assert on struct pidfd_info
> pidfd: add a new supported_mask field
> pidfs: prepare to drop exit_info pointer
> pidfs: drop struct pidfs_exit_info
> pidfs: expose coredump signal
I don't think these changes need my review... but FWIW, I see nothing
wrong in 1-8. For 1-8:
Reviewed-by: Oleg Nesterov <oleg@...hat.com>
Powered by blists - more mailing lists