From: Mike Snitzer <snitzer@redhat.com>
To: Michael Mueller <malware@t-online.de>
Cc: linux-kernel@vger.kernel.org, Kent Overstreet <kmo@daterainc.com>,
Jens Axboe <axboe@kernel.dk>, Alasdair Kergon <agk@redhat.com>,
Neil Brown <neilb@suse.de>
Subject: Re: 3.14-rc4 blocks on LVM init
Date: Tue, 25 Feb 2014 19:35:45 -0500 [thread overview]
Message-ID: <20140226003545.GA4167@redhat.com> (raw)
In-Reply-To: <530D3165.8070501@t-online.de>
On Tue, Feb 25 2014 at 7:12pm -0500,
Michael Mueller <malware@t-online.de> wrote:
> Hi,
>
> with 3.14-rc4 my box does not finish initializing the LVM array. It
> hangs within the call to rw_header() on line 632 of dm-log.c. See
> backtrace at end. Please excuse typos within - had to type it from a
> screen shot.
>
> The problem seems to be introduced by the commit
> 003b5c5719f159f4f4bf97511c4702a0638313dd (block: Convert drivers to
> immutable biovecs).
You need these two 3.14-rc fixes that are staged in linux-next (via
linux-dm.git's 'for-next' branch):
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=d73f9907294c670da14baea3fb31be27879e818e
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=f3a44fe0608eb628e1f8f6e3540462e6d171a745
I wanted to send these to Linus last week but I was waiting for some
dm-thin fixes that aren't quite ready. I'll send whatever I have staged
to Linus by this Friday so that 3.14-rc5 will have these fixes no matter
what.
Sorry for the inconvenience.
Mike
next prev parent reply other threads:[~2014-02-26 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 0:12 3.14-rc4 blocks on LVM init Michael Mueller
2014-02-26 0:35 ` Mike Snitzer [this message]
2014-02-26 2:36 ` Michael Mueller
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=20140226003545.GA4167@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malware@t-online.de \
--cc=neilb@suse.de \
/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.