From: Jens Axboe <axboe@kernel.dk>
To: Dmitrii Tcvetkov <demfloro@demfloro.ru>, linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Paolo Valente <paolo.valente@linaro.org>
Subject: Re: Bisected GFP in bfq_bfqq_expire on v5.1-rc1
Date: Fri, 29 Mar 2019 08:10:38 -0600 [thread overview]
Message-ID: <0e203a26-b941-cef4-dff1-013999d4b041@kernel.dk> (raw)
In-Reply-To: <20190329160227.7d55c8dd@fire.localdomain>
On 3/29/19 7:02 AM, Dmitrii Tcvetkov wrote:
> Hi,
>
> I got kernel panic since v5.1-rc1 when working with files on block
> device with BFQ scheduler assigned. I didn't find trivial way to
> reproduce the panic but "git checkout origin/linux-5.0.y"
> on linux-stable-rc[1] git repo on btrfs filesystem reproduces the
> problem 100% of the time on my bare-metal machine and in a VM.
>
> Bisect led me to commit 9dee8b3b057e1 (block, bfq: fix queue removal
> from weights tree). After reverting this commit on top of current
> mainline master(9936328b41ce) I can't reproduce the problem.
>
> dmesg with the panic and bisect log attached.
>
> [1] https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Paolo, can you please take a look at this?
--
Jens Axboe
next prev parent reply other threads:[~2019-03-29 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 13:02 Bisected GFP in bfq_bfqq_expire on v5.1-rc1 Dmitrii Tcvetkov
2019-03-29 14:10 ` Jens Axboe [this message]
2019-04-01 7:29 ` Paolo Valente
2019-04-01 8:55 ` Dmitrii Tcvetkov
2019-04-01 9:01 ` Paolo Valente
2019-04-01 9:22 ` Dmitrii Tcvetkov
2019-04-01 10:35 ` Paolo Valente
2019-04-04 19:22 ` Dmitrii Tcvetkov
2019-04-09 9:55 ` Paolo Valente
2019-04-09 16:14 ` Dmitrii Tcvetkov
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=0e203a26-b941-cef4-dff1-013999d4b041@kernel.dk \
--to=axboe@kernel.dk \
--cc=demfloro@demfloro.ru \
--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