From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] crypsetup segfaulting during luksFormat
Date: Wed, 7 Jul 2010 19:36:58 +0200 [thread overview]
Message-ID: <20100707173658.GA20180@tansi.org> (raw)
In-Reply-To: <1278523178.9943.5.camel@Koma-Station.localdomain>
Just a guess: Your CPU is too fast, the time
measurement for the PKBF2 iterations did not
expect that and does nonesense, resutling in
the segfault.
Tht would be a classic ;-)
Arno
On Wed, Jul 07, 2010 at 07:19:38PM +0200, Sven Eschenberg wrote:
> Hi list,
>
> I was just trying to setup a new luks device, and for some reason (I
> cannot determine yet) cryptsetup just segfaults (setting up the old
> mappings works as usual).
>
> These are the last couple lines before cryptsetup dies:
> 2370 read(4, "|\27\211<e\263\36\35j\201j\204e\326 \270\364\277\373
> \300LY[\343d[\215\32\17\315N\333", 32) = 32
> 2370 open("/dev/md125", O_RDONLY) = 5
> 2370 ioctl(5, BLKIOMIN, 0x7fff561ea000) = 0
> 2370 ioctl(5, BLKIOOPT, 0x7fff561e9ff8) = 0
> 2370 ioctl(5, BLKALIGNOFF, 0x7fff561ea00c) = 0
> 2370 close(5) = 0
> 2370 read(4, "\242\270\205|\207@\253\227 \321)\f\r/\"R>EN(wo\224\205\7e
> \36\313g\232\n\33", 32) = 32
> 2370 rt_sigaction(SIGVTALRM, {0x40d3f0, [VTALRM], SA_RESTORER|
> SA_RESTART, 0xf0000000fc0c748}, {SIG_DFL, [], 0}, 8) = 0
> 2370 setitimer(ITIMER_VIRTUAL, {it_interval={0, 0}, it_value={1, 0}},
> NULL) = 0
> 2370 --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
> 2370 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 2370 +++ killed by SIGSEGV +++
>
> where /dev/md125 is the device I am trying to setup via luksFormat.
>
> Anyone with any suggestion what the problem can be?
>
> Oh I forgot:
> cryptsetup --version
> cryptsetup 1.1.2
>
> Regards
>
> -Sven
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-07-07 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:19 [dm-crypt] crypsetup segfaulting during luksFormat Sven Eschenberg
2010-07-07 17:36 ` Arno Wagner [this message]
2010-07-07 17:49 ` Sven Eschenberg
2010-07-07 20:19 ` Arno Wagner
2010-07-07 20:44 ` Milan Broz
2010-07-07 20:58 ` Sven Eschenberg
2010-07-07 21:22 ` Milan Broz
2010-07-08 2:22 ` Sven Eschenberg
2010-07-08 9:30 ` Arno Wagner
2010-07-08 13:37 ` Sven Eschenberg
2010-07-08 14:16 ` Milan Broz
2010-07-08 14:29 ` Sven Eschenberg
2010-07-08 15:11 ` Milan Broz
2010-07-08 18:44 ` Sven Eschenberg
2010-07-09 7:22 ` Milan Broz
2010-07-09 12:18 ` Sven Eschenberg
2010-07-09 12:46 ` Milan Broz
2010-07-14 18:14 ` Christoph Anton Mitterer
2010-07-14 18:24 ` Milan Broz
2010-07-14 18:56 ` Sven Eschenberg
2010-07-07 21:40 ` Milan Broz
2010-07-07 22:00 ` Arno Wagner
2010-07-08 2:13 ` Sven Eschenberg
2010-07-07 20:51 ` Arno Wagner
2010-07-07 18:36 ` Milan Broz
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=20100707173658.GA20180@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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