Ubuntu
cryptsetup package

  1. Bug #719388
  2. Comment #3

Comment 3 for bug 719388

Revision history for this message
dc (darkcharl) wrote :

Same behavior on luksClose:

9996 17:01:33 ioctl(3, DM_TABLE_STATUS, 0x24d6b30) = 0
9996 17:01:33 open("/dev/urandom", O_RDONLY) = 4
9996 17:01:33 read(4, "\254\231", 2) = 2
9996 17:01:33 semget(0xd4d99ac, 1, IPC_CREAT|IPC_EXCL|0600) = 557059
9996 17:01:33 semctl(557059, 0, SETVAL, 0x1) = 0
9996 17:01:33 close(4) = 0
9996 17:01:33 semop(557059, {{0, 1, 0}}, 1) = 0
9996 17:01:33 ioctl(3, DM_DEV_REMOVE, 0x24d6a50) = 0
9996 17:01:34 semget(0xd4d99ac, 1, 0) = 557059
9996 17:01:34 semop(557059, {{0, -1, IPC_NOWAIT}}, 1) = 0
9996 17:01:34 semget(0xd4d99ac, 1, 0) = 557059
9996 17:01:34 semop(557059, {{0, -1, IPC_NOWAIT}}, 1) = -1 EAGAIN (Resource temporarily unavailable)
9996 17:01:34 write(2, "semid 557059: semop failed for cookie 0xd4d99ac: incorrect semaphore state", 74) = 74
9996 17:01:34 write(2, "\n", 1) = 1
9996 17:01:34 write(2, "Failed to set a proper state for notification semaphore identified by cookie value 223189420 (0xd4d99ac) to initialize waiting for incoming notifications.", 154) = 154
9996 17:01:34 write(2, "\n", 1) = 1
9996 17:01:34 semctl(557059, 0, IPC_RMID, 0) = 0