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 1C1A2C433FE for ; Thu, 3 Nov 2022 18:31:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231605AbiKCSa6 (ORCPT ); Thu, 3 Nov 2022 14:30:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58568 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229587AbiKCSap (ORCPT ); Thu, 3 Nov 2022 14:30:45 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F305E26DE for ; Thu, 3 Nov 2022 11:29:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1667500187; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=dvDqTENSw9N0V4FMcGDKiEfPJa7hYDNehGPPO8daO5Q=; b=Sr0sTZzHt8ZmVfeSS2spfM4Ocy3pBFjKqljiFf3Wfze5jvl4zYyEOiNGnHvxIga0bLBUcB dvsaq2fHXOZ+r6DV3Ol0XwSHIJMUG6j/fgggbsUCYcyaN8RAfAp70PnxTarRxjwEooW9PA hBHxXIVdcWPOjId4e5NJ2xBCQrDhxEk= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-631-ZL1D63TdPu6FPBTVAN2-Nw-1; Thu, 03 Nov 2022 14:29:43 -0400 X-MC-Unique: ZL1D63TdPu6FPBTVAN2-Nw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 60AD21C14341; Thu, 3 Nov 2022 18:29:43 +0000 (UTC) Received: from llong.com (unknown [10.22.33.38]) by smtp.corp.redhat.com (Postfix) with ESMTP id B9A551121331; Thu, 3 Nov 2022 18:29:42 +0000 (UTC) From: Waiman Long To: Peter Zijlstra , Ingo Molnar , Will Deacon , Boqun Feng Cc: linux-kernel@vger.kernel.org, john.p.donnelly@oracle.com, Hillf Danton , Mukesh Ojha , =?UTF-8?q?Ting11=20Wang=20=E7=8E=8B=E5=A9=B7?= , Waiman Long Subject: [PATCH v5 0/6] lockinig/rwsem: Fix rwsem bugs & enable true lock handoff Date: Thu, 3 Nov 2022 14:29:30 -0400 Message-Id: <20221103182936.217120-1-longman@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org v5: - Drop patch 2 and replace it with 2 new patches disabling preemption on all reader functions and writer functions respectively. The other patches are adjusted accordingly. v4: - Update patch descriptions in patches 1 & 2 to make clear the live lock conditions that are being fixed by these patches. There is no code change from v3. v3: - Make a minor cleanup to patch 1. - Add 3 more patches to implement true lock handoff. It turns out the current waiter optimistic spinning code does not work that well if we have RT tasks in the mix. This patch series include two different fixes to resolve those issues. The last 3 patches modify the handoff code to implement true lock handoff similar to that of mutex. Waiman Long (6): locking/rwsem: Prevent non-first waiter from spinning in down_write() slowpath locking/rwsem: Disable preemption at all down_read*() and up_read() code paths locking/rwsem: Disable preemption at all down_write*() and up_write() code paths locking/rwsem: Change waiter->hanodff_set to a handoff_state enum locking/rwsem: Enable direct rwsem lock handoff locking/rwsem: Update handoff lock events tracking kernel/locking/lock_events_list.h | 6 +- kernel/locking/rwsem.c | 237 ++++++++++++++++++++++-------- 2 files changed, 181 insertions(+), 62 deletions(-) -- 2.31.1