Linux Device Mapper development
 help / color / mirror / Atom feed
From: Ondrej Kozina <okozina@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: kkolasa@winsoft.pl, mpatocka@redhat.com, agk@redhat.com,
	snitzer@redhat.com
Subject: Re: commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
Date: Mon, 18 Aug 2014 16:04:11 +0200	[thread overview]
Message-ID: <53F207DB.5090909@redhat.com> (raw)
In-Reply-To: <53F0F7C7.2010501@winsoft.pl>

On 08/17/2014 08:43 PM, Krzysztof Kolasa wrote:
> On x86 after truecrypt mount device system freezes.
>
> console: truecrypt --mount, last argument (admin,user password) after
> Enter - create oops on console, system freezes
> gnome shell: when mount truecrypt drive - freezes system
>
> On x86_64 all working OK.
>
> revert commit [ 298a9fa dm crypt: use per-bio data ] restores the
> ability to use truecrypt on 3.17-rc1 x86 kernel
>
> Krzysztof
>

Hi Krzysztof,

please could you share more details about your setup? I couldn't 
reproduce the crash you wrote about. I tried with truecrypt 7.1 and 
cryptsetup-1.6.4 with no 'success'. What cipher did you use? I tried 
with aes-xts-plain64...

Kind regards
O.

  reply	other threads:[~2014-08-18 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17 18:43 commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes ) Krzysztof Kolasa
2014-08-18 14:04 ` Ondrej Kozina [this message]
2014-08-18 15:15 ` Alasdair G Kergon
2014-08-18 15:37   ` Milan Broz
2014-08-18 17:33   ` Krzysztof Kolasa
2014-08-18 18:36     ` [PATCH] dm-crypt: Fix per-bio data alignment Milan Broz
2014-08-18 19:32       ` Krzysztof Kolasa
2014-08-19 18:37       ` Mikulas Patocka
2014-08-19 19:41         ` Milan Broz
2014-08-27 16:18           ` Mikulas Patocka

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=53F207DB.5090909@redhat.com \
    --to=okozina@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kkolasa@winsoft.pl \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox