linux-kernel - Re: 3.14-rc4 blocks on LVM init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Feb 2014 19:35:45 -0500
From:	Mike Snitzer <snitzer@...hat.com>
To:	Michael Mueller <malware@...nline.de>
Cc:	linux-kernel@...r.kernel.org, Kent Overstreet <kmo@...erainc.com>,
	Jens Axboe <axboe@...nel.dk>, Alasdair Kergon <agk@...hat.com>,
	Neil Brown <neilb@...e.de>
Subject: Re: 3.14-rc4 blocks on LVM init

On Tue, Feb 25 2014 at  7:12pm -0500,
Michael Mueller <malware@...nline.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/