Comment 23 for bug 148003

Unfortunately I still occasionally get the temporary-cryptsetup mapping left around (as shown by sudo dmsetup ls), though this is much less frequent now. I'm afraid that race conditions are probably endemic due to the design of udev; the way it forks processes into the background it seems like there is no guarantee that create/remove events will be handled in the right order. I wish I knew why this all worked (for me) under Gutsy.