From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: for-4.12/block branch
Date: Fri, 21 Apr 2017 11:53:44 -0600 [thread overview]
Message-ID: <bf1227a6-e295-da91-e0d8-6767162f68b1@kernel.dk> (raw)
In-Reply-To: <1492796361.2550.22.camel@sandisk.com>
On 04/21/2017 11:39 AM, Bart Van Assche wrote:
> On Fri, 2017-04-21 at 11:07 -0600, Jens Axboe wrote:
>> Let me know what that bisection yields.
>
> Hello Jens,
>
> Although I still have to double-check the result, this is what git bisect
> reported:
>
> b00c53e8f411a0b2be036c41852c6858541afbf7 is the first bad commit
> commit b00c53e8f411a0b2be036c41852c6858541afbf7
> Author: Jens Axboe <axboe@fb.com>
> Date: Thu Apr 20 16:40:36 2017 -0600
>
> blk-mq: fix schedule-while-atomic with scheduler attached
>
> I have attached my kernel config to this e-mail. Please let me know if you
> need more information.
That would have been my prime suspect as well, since it is fiddling
with the preempt counts. I'll double check the patch.
--
Jens Axboe
prev parent reply other threads:[~2017-04-21 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 15:32 for-4.12/block branch Bart Van Assche
2017-04-21 16:25 ` Jens Axboe
2017-04-21 16:31 ` Bart Van Assche
2017-04-21 16:33 ` Jens Axboe
2017-04-21 16:40 ` Bart Van Assche
2017-04-21 16:48 ` Jens Axboe
2017-04-21 16:56 ` Jens Axboe
2017-04-21 17:05 ` Bart Van Assche
2017-04-21 17:07 ` Jens Axboe
2017-04-21 17:12 ` Jens Axboe
2017-04-21 17:39 ` Bart Van Assche
2017-04-21 17:53 ` Jens Axboe [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=bf1227a6-e295-da91-e0d8-6767162f68b1@kernel.dk \
--to=axboe@kernel.dk \
--cc=Bart.VanAssche@sandisk.com \
--cc=linux-block@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.