Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933455AbbLTNVF (ORCPT ); Sun, 20 Dec 2015 08:21:05 -0500 Received: from terminus.zytor.com ([198.137.202.10]:49680 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932948AbbLTNVB (ORCPT ); Sun, 20 Dec 2015 08:21:01 -0500 Date: Sun, 20 Dec 2015 05:20:23 -0800 From: tip-bot for Darren Hart Message-ID: Cc: peterz@infradead.org, dave@stgolabs.net, linux-kernel@vger.kernel.org, dvhart@linux.intel.com, mingo@kernel.org, tglx@linutronix.de, mtk.manpages@gmail.com, hpa@zytor.com Reply-To: dvhart@linux.intel.com, mingo@kernel.org, mtk.manpages@gmail.com, hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org, peterz@infradead.org, dave@stgolabs.net In-Reply-To: <9f3bdc116d79d23f5ee72ceb9a2a857f5ff8fa29.1450474525.git.dvhart@linux.intel.com> References: <9f3bdc116d79d23f5ee72ceb9a2a857f5ff8fa29.1450474525.git.dvhart@linux.intel.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:locking/core] futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op Git-Commit-ID: 337f13046ff03717a9e99675284a817527440a49 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2102 Lines: 51 Commit-ID: 337f13046ff03717a9e99675284a817527440a49 Gitweb: http://git.kernel.org/tip/337f13046ff03717a9e99675284a817527440a49 Author: Darren Hart AuthorDate: Fri, 18 Dec 2015 13:36:37 -0800 Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:25 +0100 futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op 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. Reported-by: Michael Kerrisk Signed-off-by: Darren Hart Cc: Peter Zijlstra Cc: Davidlohr Bueso Link: http://lkml.kernel.org/r/9f3bdc116d79d23f5ee72ceb9a2a857f5ff8fa29.1450474525.git.dvhart@linux.intel.com Signed-off-by: Thomas Gleixner --- kernel/futex.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kernel/futex.c b/kernel/futex.c index 461d438..8a310e2 100644 --- a/kernel/futex.c +++ b/kernel/futex.c @@ -3084,7 +3084,8 @@ long do_futex(u32 __user *uaddr, int op, u32 val, ktime_t *timeout, if (op & FUTEX_CLOCK_REALTIME) { flags |= FLAGS_CLOCKRT; - if (cmd != FUTEX_WAIT_BITSET && cmd != FUTEX_WAIT_REQUEUE_PI) + if (cmd != FUTEX_WAIT && cmd != FUTEX_WAIT_BITSET && \ + cmd != FUTEX_WAIT_REQUEUE_PI) return -ENOSYS; } -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/