From: Paolo Valente <firstname.lastname@example.org>
To: Mike Galbraith <email@example.com>
Cc: lkml <firstname.lastname@example.org>,
Subject: Re: block, bfq: NULL pointer dereference in bfq_rq_pos_tree_lookup()
Date: Wed, 12 May 2021 11:49:34 +0200 [thread overview]
Message-ID: <DB1E4403-5102-4D01-A8F6-2F12191F7761@linaro.org> (raw)
> Il giorno 8 mag 2021, alle ore 06:49, Mike Galbraith <email@example.com> ha scritto:
> 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.
Not easy to debug this way :)
At any rate, I've just posted the fix contained in my debug patch series.
prev parent reply other threads:[~2021-05-12 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
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
2021-05-12 9:49 ` Paolo Valente [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).