Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2468146pxj; Mon, 10 May 2021 03:50:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx6FJVzYbquTnAQNHkwSTxOfR3+HTyeptg0eUT+A02lJIlOCT1NCJb//mJRGtlUXR4oB4SU X-Received: by 2002:a92:c884:: with SMTP id w4mr20809544ilo.186.1620643818433; Mon, 10 May 2021 03:50:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620643818; cv=none; d=google.com; s=arc-20160816; b=NhtNCi/flhSrucrq+PSOUrwuuztNpWXVbD5NlpDyT9UuGJ1JJ2yecoK8R7eDzyEA5x bKPoEQGPXElHa8Rh4vMjG6+Mp96QJ0hCKLNTuCfAy2qqpAQg1A6qVIMPUOStVlFEmLGT 9sni1BKUlyOlbszntb+6VHumd6QD27B9hYOFS9zhlpKcnY+lhPPwVjsFN2MLCsx/aqmc RGVbcVhFfKIr6R7mX+Q2I5N0gPI8vjLXO4qxN4km74yyiNoD9RPRnrJhHpQXAC8MuYvL EudtaVblNNFjbhper1NJAsF9B3RRIupu4F1K8hu1TWR0oy0Gd64dF7ARqn8FCf3Cbqh5 400Q== 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=cXmhzS5VPiNvMB/UKagIY4uifiRESXwAN2brE132u0A=; b=sVE1JWAkVxSu+kcp00RGdzx/kbZgrVhOb6r3yb0Req2IrFNmW0aX6U7jC+g1qUw8Co PFOK6RBwC3pwYzFKtoHN+dQmg0lj90K0APH2Ezk8VnFpCtGusoYj6rnWcpRz2AU/oRg8 ZGGZnnvlC5LwyPt6hKxbHheIYqo/V8f1r2Nvufce0QbdhdRbh0iitNqyYCP+XUzkZ9W5 hFxAfX7BXxjtNTuExlp7eEe8SV/ktRuIEDQPloec/D6U+el84yy9dlSEr1MIvazrJugf iCxhw4IQQzOnaWCKfepgZs8jJu7gbgUv+pZuBWRhcaJAn35283jXAdrJ1MJXN4vmfRdC Htyg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=tlSzJnwo; 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 s4si17590154ilv.33.2021.05.10.03.50.05; Mon, 10 May 2021 03:50:18 -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=tlSzJnwo; 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 S233041AbhEJKt0 (ORCPT + 99 others); Mon, 10 May 2021 06:49:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:50354 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231932AbhEJKjK (ORCPT ); Mon, 10 May 2021 06:39:10 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id B0A726194B; Mon, 10 May 2021 10:30:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620642617; bh=KnHG1cULDcYsMGaGBooHNXq5AglfonCgcnIsicCW4M8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=tlSzJnwoXwxpRHSAhapvNWB8T/ISNu36Xqe9h0OpTkaVJjjItuCQR05dDlGMH6K0x gdeMyo2jhIIh/f16XnDXnsNe8TgS1AFIS3JabAS+YXbWkNKDi8JBGp04APKtgTvXSJ vHy+/qoXXfflcqNWCHToWwYcZlj1JAKmMv9oMEeo= 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.4 160/184] Revert 337f13046ff0 ("futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op") Date: Mon, 10 May 2021 12:20:54 +0200 Message-Id: <20210510101955.353855426@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210510101950.200777181@linuxfoundation.org> References: <20210510101950.200777181@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 @@ -3862,8 +3862,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; }