3.8.5: incorrect semaphore state issue

[Udo van den Heuvel]

Hello,

This morning I did a luksOpen on an external harddisk and saw:

# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie value 223205083 (0xd4dd6db) to initialize waiting for incoming
notifications.
# mount /dev/mapper/crypto2 /media
#

So stuff worked OK, just the unexpected messages.
I did find an ubuntu bug from 2011 so what needs fixing this time?

Please advise!

Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/