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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5313DC001DC for ; Wed, 26 Jul 2023 19:54:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232158AbjGZTy4 (ORCPT ); Wed, 26 Jul 2023 15:54:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230315AbjGZTyx (ORCPT ); Wed, 26 Jul 2023 15:54:53 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 16CB426A6 for ; Wed, 26 Jul 2023 12:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=uQtg7bF8jO9wCtSaK/MwXeMPoj7DNzEunPVvhTy7B7w=; b=Autuc1dtXMh3LmG7zFivT+nsBZ e/zaY0iH68e8vBtFcruaESTyK1l1zUZL+TvJYApc23Qg0V/rv2bCO9YHr6XWzJ9iF0IQcHYFM3G7W 517jkdFj6aI5YpcIgncyndlq1ehnhH0QJPZ6y7jstiyGIKcptrl4mi65V8UXSdkYzu+F2KW1hXY0v CCjJgCcr7X4N5HtnMQMl73D7O1UvFBBueOOihYfAre/yZOajffVwTzx5IAyJJBxccNXLjoYjBotFe CaK4bmeCNtMqb9DwnGm+ElZ4ZW19ovGAjRYFDhWJtsUgfliGyW/aCxIr30H6aWSiCDtVtbd6Ab5dH /jybaIFg==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1qOkam-006njw-5b; Wed, 26 Jul 2023 19:54:42 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id 4BAB23005FA; Wed, 26 Jul 2023 21:54:39 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 0EABF205963BA; Wed, 26 Jul 2023 16:40:55 +0200 (CEST) Date: Wed, 26 Jul 2023 16:40:55 +0200 From: Peter Zijlstra To: Sebastian Andrzej Siewior Cc: triangletrap12@gmail.com, Ingo Molnar , Thomas Gleixner , Will Deacon , Waiman Long , linux-kernel@vger.kernel.org, Boqun Feng , Mike Galbraith Subject: Re: [PATCH] locking/rtmutex: Fix task->pi_waiters integrity Message-ID: <20230726144055.GV4253@hirez.programming.kicks-ass.net> References: <20230707161052.GF2883469@hirez.programming.kicks-ass.net> <20230726141253.R_LS0bsr@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230726141253.R_LS0bsr@linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 26, 2023 at 04:12:53PM +0200, Sebastian Andrzej Siewior wrote: > On 2023-07-07 18:10:52 [+0200], Peter Zijlstra wrote: > > > > Henry reported that rt_mutex_adjust_prio_check() has an ordering > > I'm going to apply it to the RT tree so it does not get lost :) It sits in tip/locking/urgent and should make it's way to Linus soon-ish.