public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	Torvald Riegel <triegel@redhat.com>,
	"Carlos O'Donell" <carlos@redhat.com>,
	Ingo Molnar <mingo@elte.hu>, Jakub Jelinek <jakub@redhat.com>,
	linux-man <linux-man@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux API <linux-api@vger.kernel.org>,
	Roland McGrath <roland@hack.frob.com>,
	Anton Blanchard <anton@samba.org>,
	Eric Dumazet <edumazet@google.com>,
	bill o gallmeister <bgallmeister@gmail.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Daniel Wagner <wagi@monom.org>, Rich Felker <dalias@libc.org>,
	Andy Lutomirski <luto@amacapital.net>,
	bert hubert <bert.hubert@netherlabs.nl>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: Next round: revised futex(2) man page for review
Date: Tue, 25 Aug 2015 23:29:58 -0700	[thread overview]
Message-ID: <20150826062958.GB50910@vmdeb7> (raw)
In-Reply-To: <alpine.DEB.2.11.1508200042180.3873@nanos>

On Thu, Aug 20, 2015 at 01:17:03AM +0200, Thomas Gleixner wrote:

...

> > >> .\" FIXME XXX In discussing errors for FUTEX_CMP_REQUEUE_PI, Darren Hart
> > >> .\"       made the observation that "EINVAL is returned if the non-pi 
> > >> .\"       to pi or op pairing semantics are violated."
> > >> .\"       Probably there needs to be a general statement about this
> > >> .\"       requirement, probably located at about this point in the page.
> > >> .\"       Darren (or someone else), care to take a shot at this?
> > > 
> > > Well, that's hard to describe because the kernel only has a limited
> > > way of detecting such mismatches. It only can detect it when there are
> > > non PI waiters on a futex and a PI function is called or vice versa.
> > 
> > Hmmm. Okay, I filed your comments away for reference, but
> > hopefully someone can help with some actual text.
> 
> I let Darren come up with something sensible :)

Heh, right, no pressure then...

I responded to Michael on this recently, copied here for reference:


FUTEX_WAIT_REQUEUE_PI can return -EINVAL if called with invalid parameters, such
as uaddr==uaddr2, or (in the case of SHARED futexes), the associated keys match
(meaning it's the same futex word - shared memory, inode, etc.). This can't
happen if the stated policy of requeueing from non-pi to pi is followed as the
same word cannot be both non-pi and pi at the same time, requiring them to be
unique futex words.

FUTEX_CMP_REQUEUE_PI will fail similarly if uaddr and uaddr2 are the same futex
word. Also, if nr_wake != 1.

But, to the point I was making above, FUTEX_CMP_REQUEUE_PI must requeue uaddr to
the same uaddr2 specified in the previous FUTEX_WAIT_REQUEUE_PI call.
FUTEX_WAIT_REQUEUE_PI sets up the operation, FUTEX_CMP_REQUEUE_PI completes it,
and they must agree on uaddr and uaddr2.


Michael, are you still looking for something more from me, or is this FIXME now
complete?



-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2015-08-26  6:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 12:07 Next round: revised futex(2) man page for review Michael Kerrisk (man-pages)
2015-07-28 20:23 ` Thomas Gleixner
2015-07-28 20:45   ` Peter Zijlstra
2015-07-28 21:03     ` Thomas Gleixner
2015-08-08  6:56       ` Michael Kerrisk (man-pages)
2015-07-29  2:09     ` Davidlohr Bueso
2015-07-29  4:11   ` Darren Hart
2015-07-29  4:21     ` Darren Hart
2015-07-29 12:00       ` Thomas Gleixner
2015-07-30  8:19       ` Michael Kerrisk (man-pages)
2015-08-08  6:53   ` Michael Kerrisk (man-pages)
2015-08-19 23:17     ` Thomas Gleixner
2015-08-26  6:29       ` Darren Hart [this message]
2015-10-07  8:30       ` Michael Kerrisk (man-pages)
2015-10-08 14:36         ` Darren Hart
2015-08-05 22:21 ` Darren Hart
2015-08-08  6:57   ` Michael Kerrisk (man-pages)
2015-08-24 21:47     ` Darren Hart
2015-08-19 22:40   ` Thomas Gleixner
2015-08-18 12:45     ` Darren Hart
2015-10-07  9:34     ` Michael Kerrisk (man-pages)
2015-10-08 14:46       ` Darren Hart
     [not found] <trinity-f9a7a25f-09e9-4409-b656-0e035dfca0b5-1438006633780@msvc-mesg-gmx010>
2015-07-27 14:44 ` Michael Kerrisk (man-pages)

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=20150826062958.GB50910@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=anton@samba.org \
    --cc=arnd@arndb.de \
    --cc=bert.hubert@netherlabs.nl \
    --cc=bgallmeister@gmail.com \
    --cc=carlos@redhat.com \
    --cc=dalias@libc.org \
    --cc=dave@stgolabs.net \
    --cc=edumazet@google.com \
    --cc=jakub@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.org \
    --cc=roland@hack.frob.com \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=triegel@redhat.com \
    --cc=wagi@monom.org \
    --cc=xypron.glpk@gmx.de \
    /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