From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Fri,  6 May 2011 17:09:49 +0200 (CEST)
Message-ID: <4DC40F36.5020005@redhat.com>
Date: Fri, 06 May 2011 17:09:42 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <BANLkTinw3Hv0WEg=XqeHGmhsdDhakJ5mRg@mail.gmail.com>
 <20110502155909.GA11763@tansi.org>
 <BANLkTi=5+rtY5MRXjbPokUZJ3eGjon4Rhw@mail.gmail.com>
 <20110503043754.GB20873@tansi.org>
 <BANLkTikNOR6==J1Z+6fp=xGjtirYeb8zNw@mail.gmail.com>
 <20110503081955.GA2739@tansi.org> <4DBFD162.8070504@redhat.com>
 <87F31F97-C7E2-4306-BE1D-A8F690A95F3E@gmail.com>
In-Reply-To: <87F31F97-C7E2-4306-BE1D-A8F690A95F3E@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] luks, swap and crash
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Francois Chenais <francois.chenais@gmail.com>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>

> Here is a link about something similar on gentoo system.
> http://forums.gentoo.org/viewtopic-t-852353-start-0.html

Thanks, nice test... I was able to lock up older kernel with that
but 2.6.38.5 (and 2.6.39-rc) works without problems for me
(at least for this short test).

So I hope the problem was fixed upstream...
(There was big changes both in dmcrypt and workqueue subsystem.)

Please let me know if you can still lock the system this way
(with upstream kernel).


Milan