All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "Thomas Gleixner" <tglx@kernel.org>,
	"Keno Fischer" <keno@juliahub.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Peter Zijlstra <peterz@infradead.org>,
	Darren Hart" <dvhart@infradead.org>,
	"Davidlohr Bueso" <dave@stgolabs.net>,
	"André Almeida" <andrealmeid@igalia.com>,
	"Yang Tao" <yang.tao172@zte.com.cn>,
	"Yi Wang" <wang.yi59@zte.com.cn>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, "Oleg Nesterov" <oleg@redhat.com>
Subject: Re: [PATCH] futex: Prevent robust futex exit race more
Date: Thu, 23 Jul 2026 15:24:54 +0200	[thread overview]
Message-ID: <lhua4rh7s9l.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20260723-obgleich-kippt-gegeben-c84192e6d6bb@brauner> (Christian Brauner's message of "Thu, 23 Jul 2026 14:53:13 +0200")

* Christian Brauner:

> Fwiw, I added unique inode numbers for the lifetime of the system to
> pidfds some time ago. The inode number is allocated for every struct pid
> and available via pid->ino. A pidfd can be stat()ed to retrieve it. Just
> mentioning it in case this may be useful.

Is there an efficient way to get this without allocating a file
descriptor, and without /proc being mounted?

Thanks,
Florian


  reply	other threads:[~2026-07-23 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  3:26 [PATCH] futex: Prevent robust futex exit race more Keno Fischer
2026-07-21 12:24 ` Thomas Gleixner
2026-07-21 16:50   ` Keno Fischer
2026-07-22 14:21     ` Thomas Gleixner
2026-07-23 12:53       ` Christian Brauner
2026-07-23 13:24         ` Florian Weimer [this message]
2026-07-23 19:59         ` Keno Fischer
2026-07-23 19:44       ` Keno Fischer

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=lhua4rh7s9l.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=andrealmeid@igalia.com \
    --cc=brauner@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=keno@juliahub.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@kernel.org \
    --cc=wang.yi59@zte.com.cn \
    --cc=yang.tao172@zte.com.cn \
    /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.