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;
From:   Waiman Long <longman@redhat.com>
To:     Peter Zijlstra <peterz@infradead.org>,
        Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
        Boqun Feng <boqun.feng@gmail.com>,
        "Paul E. McKenney" <paulmck@kernel.org>,
        Davidlohr Bueso <dave@stgolabs.net>
Cc:     linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>,
        Waiman Long <longman@redhat.com>
Subject: [PATCH-tip 0/5] locking/locktorture: Fix locktorture ww_mutex test problems
Date:   Thu, 18 Mar 2021 13:28:09 -0400
Message-Id: <20210318172814.4400-1-longman@redhat.com>
Precedence: bulk

This is a follow-up patch series for the previous patchset on fixing
locktorture ww_mutex test problem [1]. The first 3 patches of that
series were merged into tip. It turns out that the last one of the
three wasn't quite right. So this patch series revert the last patch.

The rests of the patch series fix the ww_mutex testing problem in
locktorture as well as removing the DEFINE_WW_MUTEX() macro from
include/linux/ww_mutex.h.

[1] https://lore.kernel.org/lkml/20210316153119.13802-1-longman@redhat.com/

Waiman Long (5):
  locking/ww_mutex: Revert "Treat ww_mutex_lock() like a trylock"
  locking/locktorture: Fix false positive circular locking splat in
    ww_mutex test
  locking/ww_mutex: Remove DEFINE_WW_MUTEX() macro
  locking/locktorture: Pass thread id to lock/unlock functions
  locking/locktorture: locking/locktorture: Fix incorrect use of
    ww_acquire_ctx in ww_mutex test

 include/linux/ww_mutex.h     |  17 +---
 kernel/locking/locktorture.c | 146 +++++++++++++++++++++++------------
 kernel/locking/mutex.c       |   5 +-
 3 files changed, 100 insertions(+), 68 deletions(-)

-- 
2.18.1