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
Date: Mon, 28 Jun 2021 15:15:50 -0700 [thread overview]
Message-ID: <20210628221550.GJ4397@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20210628160841.GD4459@nvidia.com>
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
prev parent reply other threads:[~2021-06-28 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 15:37 Lockdep splat in -next Paul E. McKenney
2021-06-28 16:08 ` Jason Gunthorpe
2021-06-28 22:15 ` Paul E. McKenney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210628221550.GJ4397@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=liuyixian@huawei.com \
--cc=liweihang@huawei.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).