Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2519708pxj; Mon, 10 May 2021 05:05:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzehsg8Yn8vmwAAwY5+U+9Pn0O4y21Nq+8XrVFceBdxieGGtddy/Sr+mLMFYgJ0BUvKOFVV X-Received: by 2002:a6b:6615:: with SMTP id a21mr17898227ioc.161.1620648325606; Mon, 10 May 2021 05:05:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620648325; cv=none; d=google.com; s=arc-20160816; b=ILs73TqUPUTpgCJjAmJUm9+G8crVs6i1bPcdArusXo0G7q0ADPgKqIW+w2t5VoF54u RhhHkDT3TX5poqUe+iR4U9QAZARK4JgjD0r2J2QKhk/DrHPjhhwc8OdcB+erv5wzWjBa 48ReOn8bUbWLJ5yeY9UJGCk/mNoCa9obHuc83lY+iYS9d29J0JSTVvturI8A/HdQ3mhR mRnumMFdLkI0EeIZwhTPm2G/sK7k0rwqj24psP05v2A+Tu8P5C92A0yAyS1BwSGvlNt/ 2Z33+OnimzPgTT8ilVjPDhptJweWxYo1uHH1nvkMqNBFLNev1sR/OQYZxrhZbfsvhASY KYDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=wUzdr7Stb69UquvO1hmmwjW1Pbpbe366nLAZXHj56wg=; b=ZgXOIrG3XU1l/Ax+JL+rdUirsmACIgolxdnAzGzcYdPlCbSGnoZ/76pRgljeejSHbc YSjuQXYQk3aV1tsp4m4Gpw/eZ3053u7zvxhYsRdRvK27m/eT48P5oWsx3AKWhm6LChRF BrFr5QPaTVnfhFMZL2xLFZ16ChPXWYcnR92frMCDXzAArs6VCJ8UF9i0oR1iC0PDkYys F6mIJEEHb9N6+KI6SOqbCocfrMEk5jRGuwDBraG/dEJaceUNs+qbXDPyamoNlJwyg6pI pJYK8wj2/H6hA2EZPKmylPc+ijJ7LpWVe11hfVoicV4UVXvAax7KO5m5wKrfqhoqQhRa tixA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=EfOiSv0V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w13si15424900ioj.33.2021.05.10.05.05.12; Mon, 10 May 2021 05:05:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=EfOiSv0V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243540AbhEJL4J (ORCPT + 99 others); Mon, 10 May 2021 07:56:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:36600 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235092AbhEJLFk (ORCPT ); Mon, 10 May 2021 07:05:40 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id A60696144F; Mon, 10 May 2021 10:55:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620644127; bh=Zx2bPmYkn6x3qs4duJRNAp1mUpu/FHJQuFvBpqYiFMg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EfOiSv0VCkP1miqHsE4S7as55ILt0fvCRXSjq15ZZY+HEO+Vhef+nr1lrLPo0PnAw TLqSJMF9l2s2IbnPcyEN4HsQHBnhMbrvH3IdJvKI4bU2iX/rsMeOGP87Nmpz0AtQJX YNqq9EtYvJAcGF7R83N/OqSztDWaHxr3cFfYMgPY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Thomas Gleixner , "Peter Zijlstra (Intel)" Subject: [PATCH 5.11 299/342] Revert 337f13046ff0 ("futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op") Date: Mon, 10 May 2021 12:21:29 +0200 Message-Id: <20210510102019.986862491@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210510102010.096403571@linuxfoundation.org> References: <20210510102010.096403571@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Thomas Gleixner commit 4fbf5d6837bf81fd7a27d771358f4ee6c4f243f8 upstream. The FUTEX_WAIT operand has historically a relative timeout which means that the clock id is irrelevant as relative timeouts on CLOCK_REALTIME are not subject to wall clock changes and therefore are mapped by the kernel to CLOCK_MONOTONIC for simplicity. If a caller would set FUTEX_CLOCK_REALTIME for FUTEX_WAIT the timeout is still treated relative vs. CLOCK_MONOTONIC and then the wait arms that timeout based on CLOCK_REALTIME which is broken and obviously has never been used or even tested. Reject any attempt to use FUTEX_CLOCK_REALTIME with FUTEX_WAIT again. The desired functionality can be achieved with FUTEX_WAIT_BITSET and a FUTEX_BITSET_MATCH_ANY argument. Fixes: 337f13046ff0 ("futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op") Signed-off-by: Thomas Gleixner Acked-by: Peter Zijlstra (Intel) Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20210422194704.834797921@linutronix.de Signed-off-by: Greg Kroah-Hartman --- kernel/futex.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) --- a/kernel/futex.c +++ b/kernel/futex.c @@ -3712,8 +3712,7 @@ long do_futex(u32 __user *uaddr, int op, if (op & FUTEX_CLOCK_REALTIME) { flags |= FLAGS_CLOCKRT; - if (cmd != FUTEX_WAIT && cmd != FUTEX_WAIT_BITSET && \ - cmd != FUTEX_WAIT_REQUEUE_PI) + if (cmd != FUTEX_WAIT_BITSET && cmd != FUTEX_WAIT_REQUEUE_PI) return -ENOSYS; }