[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251104-akrobatisch-warnschilder-7bc99f7cfcda@brauner>
Date: Tue, 4 Nov 2025 22:00:26 +0100
From: Christian Brauner <brauner@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
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 Sun, Nov 02, 2025 at 06:03:54PM +0100, Oleg Nesterov wrote:
> 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
Hm? You're the most suited to review them for sure.
And you always find my nasty little bugs. ;)
> wrong in 1-8. For 1-8:
>
> Reviewed-by: Oleg Nesterov <oleg@...hat.com>
Thanks!
Powered by blists - more mailing lists