From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: Re: [GIT PULL 05/12 for v6.18] pidfs
Date: Tue, 7 Oct 2025 16:34:19 +0200 [thread overview]
Message-ID: <20251007143418.GA12329@redhat.com> (raw)
In-Reply-To: <20251006-liedgut-leiden-f3d51f4242c2@brauner>
On 10/06, Christian Brauner wrote:
>
> On Wed, Oct 01, 2025 at 04:18:12PM +0200, Oleg Nesterov wrote:
> > On 09/26, Christian Brauner wrote:
> > >
> > > Oleg Nesterov (3):
> > > pid: make __task_pid_nr_ns(ns => NULL) safe for zombie callers
> > ...
> > > gaoxiang17 (1):
> > > pid: Add a judgment for ns null in pid_nr_ns
> >
> > Oh... I already tried to complain twice
> >
> > https://lore.kernel.org/all/20250819142557.GA11345@redhat.com/
> > https://lore.kernel.org/all/20250901153054.GA5587@redhat.com/
> >
> > One of these patches should be reverted. It doesn't really hurt, but it makes
> > no sense to check ns != NULL twice.
>
> Sorry, those somehow got lost.
> Do you mind sending me a revert?
Thanks, will do.
But which one? I am biased, but I'd prefer to revert 006568ab4c5ca2309ceb36
("pid: Add a judgment for ns null in pid_nr_ns")
Mostly because abdfd4948e45c51b1916 ("pid: make __task_pid_nr_ns(ns => NULL)
safe for zombie callers") tries to explain why this change makes sense and
why it is not easy to avoid ns == NULL.
OK?
Oleg.
next prev parent reply other threads:[~2025-10-07 14:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 14:18 [GIT PULL 00/12 for v6.18] vfs 6.18 Christian Brauner
2025-09-26 14:18 ` [GIT PULL 01/12 for v6.18] misc Christian Brauner
2025-09-29 9:47 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 02/12 for v6.18] mount Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 03/12 for v6.18] inode Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 04/12 for v6.18] iomap Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 05/12 for v6.18] pidfs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-10-01 14:18 ` Oleg Nesterov
2025-10-06 13:48 ` Christian Brauner
2025-10-07 14:34 ` Oleg Nesterov [this message]
2025-10-10 11:00 ` Christian Brauner
2025-09-26 14:19 ` [GIT PULL 06/12 for v6.18] rust Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 07/12 for v6.18] workqueue Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 08/12 for v6.18] core kernel Christian Brauner
2025-09-27 12:19 ` Sasha Levin
2025-09-29 9:53 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 9/12 for v6.18] afs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 10/12 for v6.18] namespaces Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 11/12 for v6.18] writeback Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 12/12 for v6.18] async directory preliminaries Christian Brauner
2025-09-29 19:31 ` 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=20251007143418.GA12329@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.