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>
Subject: Re: block, bfq: NULL pointer dereference in bfq_rq_pos_tree_lookup()
Date: Sat, 08 May 2021 06:49:36 +0200 [thread overview]
Message-ID: <abe6426476d4e87bd3977079380bc7c3f508328d.camel@gmx.de> (raw)
In-Reply-To: <e0ece2e6349e92adc3da6d8c2ae6ff8a4172e4ad.camel@gmx.de>
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
next prev parent reply other threads:[~2021-05-08 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8c38408d27f1032f2a664838e523376c5da09a80.camel@gmx.de>
2021-05-03 9:52 ` block, bfq: NULL pointer dereference in bfq_rq_pos_tree_lookup() Paolo Valente
2021-05-03 12:41 ` Mike Galbraith
2021-05-08 4:49 ` Mike Galbraith [this message]
2021-05-12 9:49 ` Paolo Valente
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=abe6426476d4e87bd3977079380bc7c3f508328d.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
/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).