From: Mike Snitzer <snitzer@redhat.com>
To: Ondrej Kozina <okozina@redhat.com>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
mpatocka@redhat.com, mbroz@redhat.com
Subject: Re: dm integrity tests crash kernel (4.12-rc5)
Date: Mon, 19 Jun 2017 11:47:35 -0400 [thread overview]
Message-ID: <20170619154735.GA16472@redhat.com> (raw)
In-Reply-To: <ad400234-fde1-5ff7-246e-91ded98764e2@redhat.com>
On Mon, Jun 19 2017 at 11:16am -0400,
Ondrej Kozina <okozina@redhat.com> wrote:
> On 06/19/2017 04:20 PM, Mike Snitzer wrote:
> >
> >Looks like submit_flush_bio() is disabling/enabling interrupts from
> >interrupt context. Ondrej, does this patch fix the issue?
>
> I let it spin for 30 minutes on patched dm-integrity and everything
> seems ok now. The moment I loaded back the old one it fell on face
> almost immediately again.
OK, I'll get it staged as a fix for 4.12.
Thanks,
Mike
prev parent reply other threads:[~2017-06-19 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 11:54 dm integrity tests crash kernel (4.12-rc5) Ondrej Kozina
2017-06-19 12:11 ` [dm-devel] " Ondrej Kozina
2017-06-19 14:20 ` Mike Snitzer
2017-06-19 15:16 ` [dm-devel] " Ondrej Kozina
2017-06-19 15:47 ` Mike Snitzer [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=20170619154735.GA16472@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
--cc=okozina@redhat.com \
/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