Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2548602pxj; Mon, 10 May 2021 05:41:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwYpS1z8gh2nDyuxcwCabFoB4goO7v0pWy+7tvuL/FY9m0pfp8z4z73Wf2RMqwquf6nGzxn X-Received: by 2002:a05:6402:22c3:: with SMTP id dm3mr30210088edb.307.1620650502143; Mon, 10 May 2021 05:41:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620650502; cv=none; d=google.com; s=arc-20160816; b=ykloNVtnOhylP/1byCzg6oQUzN/VlU53wXPS3uUo88WeDk95kOkwSs41xGy79S2ZHM fpJgjUj2Pl+Cco2ohJUs/aYHQo+TROreFP9R6adDum5Q/QYiZrlHy4MeZ6FqMEF2FLfG NMYN5LEQ0LxHNy44HMAdS1K3MvIyKSPqmF1wF5YgCiSqYFP4eG122jEKjLdCJ3xTtj4y k4BBwKKnJk1oULHtVJl+g4FuqFFcJWk6hfdofZ7Siqc1sNy+fjN3hbr+f4y2aGs25SY/ +hiZnPG0ALIw5Cb5ENn/+34lCsDz20+flfhwE1xNa0MYxfdww4YyeH8ZIaqjQSjPnOex vgEg== 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=+HFrQIJvqKyFb9lcY3riPt6uOwO74VekN9MM3JeLNj4=; b=V6iTdJnUUBccHWxOcX5qn6zP46+T3LOspOHPQGsOBA3eX5X8/ReGuPH//cPxlCrCzy FAlN5hjtYs4qL5seWZvnQIIiILBqDZMMHpcO6EMpYdOFhHvWt0vw0Vi/9hMk8KJU2637 aSHHR1i1abRhg1vbubIAbTwEAbauDmNI9Uj+5ESHMR51myQ6cywPwlZAdE7Hz0T1TqxE fRl81SvMq7vlxqQeJPO3U8JmrzAqqzPv84iZIkIhQsRBkICoGlKaUBzepLZgJt9nReuZ Dmwj8tN9lwugoRgDyvZRaIQ2RLX04BeuzyEBUlcUYc3v77hNkzgt5nJnoUV67a4RnlT8 KkAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="wr/Rj2Qf"; 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 y4si12967662eds.430.2021.05.10.05.41.18; Mon, 10 May 2021 05:41:42 -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="wr/Rj2Qf"; 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 S1347640AbhEJMgl (ORCPT + 99 others); Mon, 10 May 2021 08:36:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:56146 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235318AbhEJLOR (ORCPT ); Mon, 10 May 2021 07:14:17 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7B0C961075; Mon, 10 May 2021 11:10:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620645056; bh=id582z2zHgIDtFnlOdn0Ci+tIXY+YTX5iV853NXKwEs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=wr/Rj2Qf+4OqRlOsBMMRW9thLqW0XzyNnFiHd9JpKSOk7FTsO7OHvohq6nuvz9fEc 9BX/cDDcjnL4qUc9872GSQNz47Nl7EIX8IG/PcWiAwLE/vEkoDXgE0m7cqVZA341aK ABzqbwFdmsWo53tF7BBDbu3mmHQtACWDlS9FDa3Y= 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.12 332/384] Revert 337f13046ff0 ("futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op") Date: Mon, 10 May 2021 12:22:01 +0200 Message-Id: <20210510102025.735241788@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210510102014.849075526@linuxfoundation.org> References: <20210510102014.849075526@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 @@ -3711,8 +3711,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; }