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;
Date:   Mon, 28 Jun 2021 15:15:50 -0700
From:   "Paul E. McKenney" <paulmck@kernel.org>
To:     Jason Gunthorpe <jgg@nvidia.com>
Cc:     liuyixian@huawei.com, liweihang@huawei.com, sfr@canb.auug.org.au,
        linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Lockdep splat in -next
Message-ID: <20210628221550.GJ4397@paulmck-ThinkPad-P17-Gen-1>
Reply-To: paulmck@kernel.org
References: <20210628153746.GA2237462@paulmck-ThinkPad-P17-Gen-1>
 <20210628160841.GD4459@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210628160841.GD4459@nvidia.com>
Precedence: bulk

On Mon, Jun 28, 2021 at 01:08:41PM -0300, Jason Gunthorpe wrote:
> On Mon, Jun 28, 2021 at 08:37:46AM -0700, Paul E. McKenney wrote:
> > Hello, Yixian Liu,
> > 
> > The following -next commit results in a lockdep splat:
> > 
> > 591f762b2750 ("RDMA/hns: Remove the condition of light load for posting DWQE")
> > 
> > The repeat-by is as follows:
> > 
> > tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --trust-make --duration 1 --configs TASKS01
> > 
> > The resulting splat is as shown below.  This appears to have been either
> > fixed or obscured by a later commit, but it does affect bisectability.
> > Which I found out about the hard way.  ;-)
> 
> I'm confused, the hns driver is causing this, and you are able to test
> with the hns hardware???

Apparently I am as well, apologies for the noise.  I incorrectly assumed
that v5.13-rc1 was clean, but this deadlock really is present in v5.13-rc.

And here I thought I was handling the heat relatively well...

							Thanx, Paul