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;
Message-ID: <abe6426476d4e87bd3977079380bc7c3f508328d.camel@gmx.de>
Subject: Re: block, bfq: NULL pointer dereference in bfq_rq_pos_tree_lookup()
From:   Mike Galbraith <efault@gmx.de>
To:     Paolo Valente <paolo.valente@linaro.org>
Cc:     lkml <linux-kernel@vger.kernel.org>,
        linux-block <linux-block@vger.kernel.org>
Date:   Sat, 08 May 2021 06:49:36 +0200
In-Reply-To: <e0ece2e6349e92adc3da6d8c2ae6ff8a4172e4ad.camel@gmx.de>
References: <8c38408d27f1032f2a664838e523376c5da09a80.camel@gmx.de>
         <9732EA9F-E15B-48E1-9B92-2D74F75C6331@linaro.org>
         <e0ece2e6349e92adc3da6d8c2ae6ff8a4172e4ad.camel@gmx.de>
Content-Type: text/plain; charset="ISO-8859-15"
User-Agent: Evolution 3.34.4 
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, 2021-05-03 at 14:41 +0200, Mike Galbraith wrote:
> On Mon, 2021-05-03 at 11:52 +0200, Paolo Valente wrote:
> > Hi Mike,
> > I've waited a little bit before replying, because I've worked on a dev
> > patch series, for debugging another crash. I'd like to use
> > this series for your failure too, as the OOPS you report
> > unfortunately does not ring any bell :(
> >
> > So, could you please try to apply this patch series?  If it doesn't
> > apply, I'll rebase it.
>
> This bug isn't deterministic, but I can wedge your set into my devel
> trees, and see if anything falls out.

What fell out was not the least bit useful.  After days of box working
just fine despite bug being given ample enticement, it didn't take the
bait.  I then build master sans patch set, which exploded on its very
first distro build, after which bug (snickered mightily and) went back
to into hiding.

	-Mike