From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932281AbbJHMjB (ORCPT ); Thu, 8 Oct 2015 08:39:01 -0400 Received: from m12-17.163.com ([220.181.12.17]:46263 "EHLO m12-17.163.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751014AbbJHMjA (ORCPT ); Thu, 8 Oct 2015 08:39:00 -0400 Date: Thu, 8 Oct 2015 05:38:49 -0700 From: Geliang Tang To: Giedrius =?utf-8?Q?Statkevi=C4=8Dius?= Cc: snitzer , linux-raid , linux-kernel Subject: Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine Message-ID: <20151008123849.GA4279@ubuntu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-CM-TRANSID: EcCowACXc_XaYxZWX9VWDg--.2744S3 X-Coremail-Antispam: 1Uf129KBjvdXoWruFy3Aw43Zr45tFWxuFyxuFg_yoW3uFg_u3 ykGw4Fy39rJr4jyw1fJ3W5Ars8JFZ7XFy8ZFnxWr10gFyjvrs5ta13XFs5XF1fC34kZrs0 kr9Yq390g34jvjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IUnb4S7UUUUU== X-Originating-IP: [218.17.162.133] X-CM-SenderInfo: 5jhoxtpqjwt0rj6rljoofrz/1tbiNRuNmVSIJWh6iAAAsZ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 07, 2015 at 10:27:27PM +0300, Giedrius Statkevičius wrote: > Hello, > I have a LUKS on LVM setup: /boot is unencrypted and everything is "hidden" in > /dev/sda2. After booting on linux-next and just after entering my password > cryptsetup segfaults and a stack trace is printed from the kernel. Since writing > down all those numbers is hard I've made a picture where it is shown: > https://i.imgur.com/6PHNUdv.jpg > > I figured it had something to do with changes to memory management and thus find > out that commit 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke my system. > Reverting it there is no such error anymore and system boots fine past that > point. > > Could someone look into this? Thanks, Giedrius Bugfix for this has been sended out. https://lkml.org/lkml/2015/10/8/342. Thanks.