Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755583AbYGYB3R (ORCPT ); Thu, 24 Jul 2008 21:29:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752818AbYGYB3B (ORCPT ); Thu, 24 Jul 2008 21:29:01 -0400 Received: from saeurebad.de ([85.214.36.134]:47041 "EHLO saeurebad.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752000AbYGYB3A (ORCPT ); Thu, 24 Jul 2008 21:29:00 -0400 From: Johannes Weiner To: Herbert Xu Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: crypto stuff broken in -mm? References: <87ljzwh3j3.fsf@saeurebad.de> <20080724074306.GA5071@gondor.apana.org.au> Date: Fri, 25 Jul 2008 03:28:35 +0200 In-Reply-To: <20080724074306.GA5071@gondor.apana.org.au> (Herbert Xu's message of "Thu, 24 Jul 2008 15:43:06 +0800") Message-ID: <874p6eg3b0.fsf@saeurebad.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.1.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 951 Lines: 26 Herbert Xu writes: > On Sun, Jul 20, 2008 at 05:24:48PM +0000, Johannes Weiner wrote: >> >> I can not access my encrypted partitions with -mm while they work with >> mainline. >> >> For both trees I have similar configs, I didn't change anything relative >> to this subsystem: > > I can't reproduce this problem here. I've created an encrypted > volume with 2.6.23 and it still decrypts correctly with the latest > upstream Linux kernel which has all the crypto updates. > > So it looks like one of the other patches in mm that's causing > this. Please try backing out any device mapper related changes > and see if things improve. It works with next-20080724. Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/