From: Alexander Duyck <alexander.duyck@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Benjamin Block <bblock@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
dm-devel@redhat.com, linux-next@vger.kernel.org,
Mikulas Patocka <mpatocka@redhat.com>,
Steffen Maier <maier@linux.ibm.com>,
Michael Holzheu <holzheu@linux.ibm.com>
Subject: Re: linux-next: Boot hangs 3 minutes with device mapper on s390
Date: Tue, 5 Mar 2019 10:02:52 -0800 [thread overview]
Message-ID: <CAKgT0UeZ26BDr2FzKKECPLgCfij0SwPrk7GA+UuUuf0nnp3S1A@mail.gmail.com> (raw)
In-Reply-To: <20190305040321.GA21739@redhat.com>
On Mon, Mar 4, 2019 at 8:03 PM Mike Snitzer <snitzer@redhat.com> wrote:
>
> Hi,
>
> Alexander reported this same boot hang in another thread. I was able to
> reproduce using an x86_64 .config that Alexander provided.
>
> I've pushed this fix out to linux-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.1&id=be2c5301817833f692aadb2e5fa209582db01d3b
>
> If you could verify this fix works for you I'd appreciate it.
>
> Thanks,
> Mike
I've verified I am no longer seeing the issue with this patch applied.
Thanks.
- Alex
next prev parent reply other threads:[~2019-03-05 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190301183350.5ff697d4@TP-holzheu>
2019-03-01 18:30 ` linux-next: Boot hangs 3 minutes with device mapper on s390 Mike Snitzer
2019-03-04 10:01 ` Steffen Maier
2019-03-04 10:03 ` Michael Holzheu
2019-03-05 4:03 ` Mike Snitzer
2019-03-05 9:46 ` Mikulas Patocka
2019-03-05 13:29 ` Mike Snitzer
2019-03-05 18:02 ` Alexander Duyck [this message]
2019-03-05 22:21 ` bio-based DM's "noclone" changes have been dropped from 5.1 [was: Re: linux-next: Boot hangs 3 minutes with device mapper on s390] Mike Snitzer
2019-03-07 10:18 ` Michael Holzheu
[not found] ` <alpine.LRH.2.02.1903011516160.20592@file01.intranet.prod.int.rdu2.redhat.com>
2019-03-01 20:30 ` linux-next: Boot hangs 3 minutes with device mapper on s390 Mike Snitzer
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=CAKgT0UeZ26BDr2FzKKECPLgCfij0SwPrk7GA+UuUuf0nnp3S1A@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=bblock@linux.ibm.com \
--cc=dm-devel@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=maier@linux.ibm.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).