public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
	brauner@kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] pid: cosmetic changes to alloc_pid()
Date: Sat, 7 Mar 2026 13:11:27 +0100	[thread overview]
Message-ID: <aawV7-yjMAy8TF7h@redhat.com> (raw)
In-Reply-To: <CAGudoHHgTA4-50qLFvptDmg1r9FB8G0TxdX7OrWoRoHgtZW_HQ@mail.gmail.com>

On 03/07, Mateusz Guzik wrote:
>
> On Sat, Mar 7, 2026 at 10:23 AM Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > On 03/06, Mateusz Guzik wrote:
> > >
> > > Commit 6d864a1b182532e7 ("pid: only take pidmap_lock once on alloc")
> > > landed v2 of the patch instead of v3. This patch remedies the problem.
> > >
> > > No functional changes.
> > >
> > > Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> >
> > The patch looks obviously good, but it conflicts with Pavel's
> >
> >         [PATCH v4 0/4] pid_namespace: make init creation more flexible
> >         https://lore.kernel.org/all/20260225133229.550302-1-ptikhomirov@virtuozzo.com/#t
> >
> > In particular, this change:
> >
> >  -     for (tmp = ns, i = ns->level; i >= 0; i--) {
> >  +     for (tmp = ns, i = ns->level; i >= 0;) {
> >
> > With 2/4 from Pavel we need to decrement "i" before the ->child_reaper
> > check.
> >
>
> That patch will be fine as it modifies the other loop which already
> had i-- towards the end.
>
> So I don't think there is any need to rebase.

Indeed, I misread your patch, sorry for noise.

Oleg.



  reply	other threads:[~2026-03-07 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 19:01 [PATCH] pid: cosmetic changes to alloc_pid() Mateusz Guzik
2026-03-07  9:23 ` Oleg Nesterov
2026-03-07 10:31   ` Mateusz Guzik
2026-03-07 12:11     ` Oleg Nesterov [this message]
2026-03-13 12:05       ` Pavel Tikhomirov

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=aawV7-yjMAy8TF7h@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mjguzik@gmail.com \
    --cc=ptikhomirov@virtuozzo.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