From: Julien Grall <julien.grall@citrix.com>
To: Jens Axboe <axboe@fb.com>, <ming.lei@canonical.com>
Cc: <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: ARM64 DOM0 crashing after commit 578270b "block: fix segment split"
Date: Mon, 30 Nov 2015 20:49:24 +0000 [thread overview]
Message-ID: <565CB654.2060005@citrix.com> (raw)
In-Reply-To: <565CABAF.7000707@fb.com>
Hi Jens,
On 30/11/2015 20:03, Jens Axboe wrote:
>> The bisector fingered the commit 578270b "block: fix segment split".
>> If I reverted this patch on top of 4.4-rc3 and everything seems to
>> work fine.
>>
>> Anyone have any ideas?
>
> Can you try my for-linus branch?
I pulled this branch into Linus' master and the problem disappear, thank
you!
Next time I will try your branch before sending an error report.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-11-30 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 18:22 ARM64 DOM0 crashing after commit 578270b "block: fix segment split" Julien Grall
2015-11-30 20:03 ` Jens Axboe
2015-11-30 20:49 ` Julien Grall [this message]
2015-11-30 20:51 ` Jens Axboe
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=565CB654.2060005@citrix.com \
--to=julien.grall@citrix.com \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=xen-devel@lists.xen.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