public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op
Date: Fri, 18 Dec 2015 16:49:21 -0800	[thread overview]
Message-ID: <20151219004921.GG17386@linux-uzut.site> (raw)
In-Reply-To: <9f3bdc116d79d23f5ee72ceb9a2a857f5ff8fa29.1450474525.git.dvhart@linux.intel.com>

On Fri, 18 Dec 2015, Darren Hart wrote:

>While reviewing Michael Kerrisk's recent futex manpage update, I noticed
>that we allow the FUTEX_CLOCK_REALTIME flag for FUTEX_WAIT_BITSET but
>not for FUTEX_WAIT.
>
>FUTEX_WAIT is treated as a simple version for FUTEX_WAIT_BITSET
>internally (with a bitmask of FUTEX_BITSET_MATCH_ANY). As such, I cannot
>come up with a reason for this exclusion for FUTEX_WAIT.
>
>This change does modify the behavior of the futex syscall, changing a
>call with FUTEX_WAIT | FUTEX_CLOCK_REALTIME from returning -ENOSYS, to be
>equivalent to FUTEX_WAIT_BITSET | FUTEX_CLOCK_REALTIME with a bitset of
>FUTEX_BITSET_MATCH_ANY.
>
>Cc: Thomas Gleixner <tglx@linutronix.de>
>Cc: Peter Zijlstra <peterz@infradead.org>
>Cc: Davidlohr Bueso <dave@stgolabs.net>
>Reported-by: Michael Kerrisk <mtk.manpages@gmail.com>
>Signed-off-by: Darren Hart <dvhart@linux.intel.com>

Acked-by: Davidlohr Bueso <dave@stgolabs.net>

  reply	other threads:[~2015-12-19  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 21:36 [PATCH] futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op Darren Hart
2015-12-19  0:49 ` Davidlohr Bueso [this message]
2015-12-20 13:20 ` [tip:locking/core] " tip-bot for Darren Hart

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=20151219004921.GG17386@linux-uzut.site \
    --to=dave@stgolabs.net \
    --cc=dvhart@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.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