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:   Boqun Feng <boqun.feng@gmail.com>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
        Waiman Long <longman@redhat.com>,
        Boqun Feng <boqun.feng@gmail.com>,
        linux-kernel@vger.kernel.org,
        Johannes Berg <johannes@sipsolutions.net>
Subject: [PATCH 0/4] Fix issues in check_irq_usage()
Date:   Sat, 19 Jun 2021 01:01:06 +0800
Message-Id: <20210618170110.3699115-1-boqun.feng@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Peter,

As we talked in IRC, Johannes Berg reported a problem and I could
reproduce by the selftest case in patch #4, there are three issues:

1)	printing of backwards dependency path doesn't work as expected,

2)	we have unnecessary and incorrect save_trace() call

3)	check_irq_usage() may result in a wrong depedency path (when a
	real one really exits).

Fix them separately in patch 1~3.

Regards,
Boqun

Boqun Feng (4):
  locking/lockdep: Fix the dep path printing for backwards BFS
  locking/lockdep: Remove the unnecessary trace saving
  lockding/lockdep: Avoid to find wrong lock dep path in
    check_irq_usage()
  locking/selftests: Add a selftest for check_irq_usage()

 kernel/locking/lockdep.c | 123 +++++++++++++++++++++++++++++++++++++--
 lib/locking-selftest.c   |  65 +++++++++++++++++++++
 2 files changed, 182 insertions(+), 6 deletions(-)

-- 
2.30.2