From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 19134C4338F for ; Mon, 2 Aug 2021 14:36:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E03E460E97 for ; Mon, 2 Aug 2021 14:36:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234145AbhHBOgJ (ORCPT ); Mon, 2 Aug 2021 10:36:09 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:49520 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233925AbhHBOgI (ORCPT ); Mon, 2 Aug 2021 10:36:08 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1627914958; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TSF4LCL8KG9Cshl8MiOPlOAr1DwKy4xSuc4wY3Vs2vM=; b=WxRi9ZJT+d2IqRdsKCCgOclEBNilMr+8BPrE5czQU6pFGYdIehZfe6KaqR2roOVx/XHL3P QZIK54lbHhD0Bvr+/DvZWN/7cc3mPG6ksmcYO9OXQWlEDLhQfqoMkyekavtZja+9wW9Eh1 Bow0CvDbM5HVMVc1/DAf6bnJVNYKdeZ9yPRstoDnVcEnTOsKQclD3JHOWOv/d9G4AVaIhe iYoauTFTMpxM6hbQuZxvAU4bdT2YbWSyy91zkOmdJQUjaWhcOz6PR6RZ81FMZ2TPKVxq9R u1ohgY0g3BAwdN12v1pU+eihsu7fTuxynv0RjmA/Hz3nMuUoSvF9fXzFbviL8w== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1627914958; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TSF4LCL8KG9Cshl8MiOPlOAr1DwKy4xSuc4wY3Vs2vM=; b=KxCfLgzrMPJxhCO/XmmwfYcmxyIzCO/OHYRMxd6AhECAwvdHQ8SkLpIN54YdVd/E54bcik besQoaq0ke8ReLDA== To: Peter Zijlstra Cc: LKML , Ingo Molnar , Juri Lelli , Steven Rostedt , Daniel Bristot de Oliveira , Will Deacon , Waiman Long , Boqun Feng , Sebastian Andrzej Siewior , Davidlohr Bueso Subject: Re: [patch 58/63] futex: Prevent requeue_pi() lock nesting issue on RT In-Reply-To: References: <20210730135007.155909613@linutronix.de> <20210730135208.418508738@linutronix.de> Date: Mon, 02 Aug 2021 16:35:58 +0200 Message-ID: <878s1j3odt.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 02 2021 at 15:10, Peter Zijlstra wrote: > On Mon, Aug 02, 2021 at 02:56:09PM +0200, Peter Zijlstra wrote: >> static inline int futex_requeue_pi_wakeup_sync(struct futex_q *q) >> { >> + int old, new; >> >> + old = atomic_read_acquire(&q->requeue_state); >> + do { >> /* Is requeue done already? */ >> + if (old >= Q_REQUEUE_PI_DONE) >> break; > > I think that can be: return old; for slightly simpler code. Yes.