Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0
Hi.
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen /dev/sdb2 crypt-extern"
then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in drivers/md, so it seems something broke.
config extract:
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not setCONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
# CONFIG_DM_MULTIPATH is not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
# CONFIG_FUSION is not set
any ideas?
mfg
thomas
Quoted 29 lines · On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[email protected]> wrote:
Hi.
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen/dev/sdb2crypt-extern"then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in
drivers/md, so it seems something broke.config extract:
CONFIG_MD=y
#CONFIG_BLK_DEV_MDis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
#CONFIG_DM_MULTIPATHis not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
#CONFIG_FUSIONis not set
Quoted 2 lines
any ideas?
Could be DM breakage, could be udev/sysfs breakage. Is it still happening in current mainline?
And how come I'm seeing unresponded-to-for-a-week regression reports on lkml?
Quoted 29 lines · Andrew Morton
Quoted 28 lines · On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[email protected]> wrote:
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen/dev/sdb2crypt-extern"then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in
drivers/md, so it seems something broke.config extract:
CONFIG_MD=y
#CONFIG_BLK_DEV_MDis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
#CONFIG_DM_MULTIPATHis not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
#CONFIG_FUSIONis not set
Quoted 5 lines
Quoted 2 lines
any ideas?
Could be DM breakage, could be udev/sysfs breakage. Is it still happening in current mainline?
There are no obvious changes, which I would expect to cause a breakage in this area.
Quoted 2 lines
And how come I'm seeing unresponded-to-for-a-week regression reports on lkml?
It works fine with 2.6.24-rc1+ and GNOME, even without any initial shell command to set it up. Just inserting a LUKS volume, brings up a password dialog, and then mounts all automatically.
There was a timing problem fix in HAL (in 0.5.10), maybe that is what happens here.
Kay
Quoted 46 lines · Kay Sievers
Quoted 29 lines · Andrew Morton
Quoted 27 lines · On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[email protected]> wrote:
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen/dev/sdb2crypt-extern"then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in
drivers/md, so it seems something broke.config extract:
CONFIG_MD=y
#CONFIG_BLK_DEV_MDis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
#CONFIG_DM_MULTIPATHis not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
#CONFIG_FUSIONis not setQuoted 6 lines
Quoted 3 lines
any ideas?
Could be DM breakage, could be udev/sysfs breakage. Is it still happening in current mainline?
There are no obvious changes, which I would expect to cause a breakage in this area.
Quoted 3 lines
And how come I'm seeing unresponded-to-for-a-week regression reports on lkml?
Quoted 7 lines
It works fine with 2.6.24-rc1+ and GNOME, even without any initial shell command to set it up. Just inserting a LUKS volume, brings up a password dialog, and then mounts all automatically.
There was a timing problem fix in HAL (in 0.5.10), maybe that is what happens here.
Hal version is 0.5.9.1-r2.
to make things clear:
boot 2.6.23 doing "cryptsetup luksOpen /dev/sdb2 crypt-extern" -> kde asks to mount new device
boot v2.6.24-rc1-497-gb1d08ac doing "cryptsetup luksOpen /dev/sdb2 crypt-extern" -> nothing happens in kde.
same user land, different kernel.
Quoted 55 lines · Thomas Meyer
Quoted 45 lines · Kay Sievers
Quoted 29 lines · Andrew Morton
Quoted 27 lines · On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[email protected]> wrote:
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen/dev/sdb2crypt-extern"then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in
drivers/md, so it seems something broke.config extract:
CONFIG_MD=y
#CONFIG_BLK_DEV_MDis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
#CONFIG_DM_MULTIPATHis not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
#CONFIG_FUSIONis not setQuoted 6 lines
Quoted 3 lines
any ideas?
Could be DM breakage, could be udev/sysfs breakage. Is it still happening in current mainline?
There are no obvious changes, which I would expect to cause a breakage in this area.
Quoted 3 lines
And how come I'm seeing unresponded-to-for-a-week regression reports on lkml?
Quoted 7 lines
It works fine with 2.6.24-rc1+ and GNOME, even without any initial shell command to set it up. Just inserting a LUKS volume, brings up a password dialog, and then mounts all automatically.
There was a timing problem fix in HAL (in 0.5.10), maybe that is what happens here.
Hal version is 0.5.9.1-r2.
Quoted 7 lines
to make things clear:
boot 2.6.23 doing "cryptsetup luksOpen/dev/sdb2crypt-extern" -> kde asks to mount new device
boot v2.6.24-rc1-497-gb1d08ac doing "cryptsetup luksOpen/dev/sdb2crypt-extern" -> nothing happens in kde.same user land, different kernel.
Yeah, but I expect it to be a timing problem, which may show up with a new kernel. The kernel is maybe just that bit faster in the event generation, that it triggers a silly HAL bug. You probably need:
http://gitweb.freedesktop.org/?p=hal.git;a=commit;h=f3e160d0ab85f62b76400cb521b4d1b5813d0711
It's all fine here regarding LUKS volumes, therefore I wouldn't know what would be wrong at the kernel side.
Kay
Quoted 72 lines · Kay Sievers
Quoted 61 lines · Thomas Meyer
Quoted 49 lines · Kay Sievers
Quoted 30 lines · Andrew Morton
Quoted 27 lines · On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[email protected]> wrote:
I have an external hard drive with an encrypted partition. I am using kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen/dev/sdb2crypt-extern"then udev/hal/kde (?)automatically created an desktop icon. i could click this icon to mount and open the drive.
when i do the luksOpen command with v2.6.23-6597-gcfa76f0 this icon is not created anymore.
a few commits were made in
drivers/md, so it seems something broke.config extract:
CONFIG_MD=y
#CONFIG_BLK_DEV_MDis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not setCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=mCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
#CONFIG_DM_MULTIPATHis not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=y
#CONFIG_FUSIONis not setQuoted 8 lines
Quoted 4 lines
any ideas?
Could be DM breakage, could be udev/sysfs breakage. Is it still happening in current mainline?
There are no obvious changes, which I would expect to cause a breakage in this area.
Quoted 4 lines
And how come I'm seeing unresponded-to-for-a-week regression reports on lkml?
Quoted 8 lines
It works fine with 2.6.24-rc1+ and GNOME, even without any initial shell command to set it up. Just inserting a LUKS volume, brings up a password dialog, and then mounts all automatically.
There was a timing problem fix in HAL (in 0.5.10), maybe that is what happens here.
Hal version is 0.5.9.1-r2.
Quoted 8 lines
to make things clear:
boot 2.6.23 doing "cryptsetup luksOpen/dev/sdb2crypt-extern" -> kde asks to mount new device
boot v2.6.24-rc1-497-gb1d08ac doing "cryptsetup luksOpen/dev/sdb2crypt-extern" -> nothing happens in kde.same user land, different kernel.
Quoted 9 lines
Yeah, but I expect it to be a timing problem, which may show up with a new kernel. The kernel is maybe just that bit faster in the event generation, that it triggers a silly HAL bug. You probably need:
http://gitweb.freedesktop.org/?p=hal.git;a=commit;h=f3e160d0ab85f62b76400cb521b4d1b5813d0711It's all fine here regarding LUKS volumes, therefore I wouldn't know what would be wrong at the kernel side.
Yes. With hal-0.5.10 (which includes above commit) the new kernel behaves like 2.6.23 again.
mfg
thomas