[dm-crypt] crypsetup segfaulting during luksFormat

Sven Eschenberg sven at whgl.uni-frankfurt.de
Wed Jul 7 19:49:04 CEST 2010


Hummm,

should I consider this geek humor or are you serious, the CPU is rather
slow (imho)?

Anyway, tweaking the iterationcount didn't chaneg a thing, messing with
the params did not help either.

The Backtrace does not really help a lot, I guess:

(gdb) bt
#0  0x000000000040d3fe in sigvtalarm ()
#1  0x0f0000000fc0c748 in ?? ()
#2  0x0000000000000000 in ?? ()

Well at least we know the crash happens in sigvtalarm, which I assume is
a signal handler of some sort within cryptsetup.

Regards

-Sven

On Wed, 2010-07-07 at 19:36 +0200, Arno Wagner wrote:
> 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 at saout.de
> > http://www.saout.de/mailman/listinfo/dm-crypt
> > 
> 




More information about the dm-crypt mailing list