[pkg-cryptsetup-devel] Bug#590125: cryptsetup update leads to udev messages on boot (rename of temporary unencrypted swap device)

[bs.net]

Package: cryptsetup
Version: 2:1.1.3-1

On my system the swap partition is defined as encrypted partition with 
cryptsetup.

/etc/crypttab:
# <target name> <source device>         <key file>      <options>
swap    /dev/sda5    /dev/urandom    swap,cipher=aes-cbc-
essiv:sha256,size=256,hash=sha256

/etc/fstab:
/dev/mapper/swap                  none            swap           sw                                               
0    0

Since the update of cryptsetup to version 1.1.3-1 I'm getting this message on 
boot:
The node /dev/mapper/swap_unformatted should have been renamed to 
/dev/mapper/swap by udev but new node is not present. Falling back to direct 
node rename.

It seems that "dmsetup rename" (used in /lib/cryptsetup/cryptdisks.functions) 
and udev does not work nicely together. In older versions of cryptosetup I did 
not got this message, because /dev/mapper/swap were created directly.

Some facts about my configuration:
* vanilla kernel 2.6.35-rc6 build with Debian config file from experimental 
linux-2.6 version and make-kpkg
* dmsetup version is 2:1.02.48-2
* udev version is 158-1