* Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 @ 2007-10-21 19:23 Thomas Meyer 2007-10-29 7:18 ` Andrew Morton 0 siblings, 1 reply; 6+ messages in thread From: Thomas Meyer @ 2007-10-21 19:23 UTC (permalink / raw) To: Linux Kernel Mailing List 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 set CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=y CONFIG_DM_SNAPSHOT=m CONFIG_DM_MIRROR=m CONFIG_DM_ZERO=m # CONFIG_DM_MULTIPATH is not set CONFIG_DM_DELAY=m CONFIG_DM_UEVENT=y # CONFIG_FUSION is not set any ideas? mfg thomas ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 2007-10-21 19:23 Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 Thomas Meyer @ 2007-10-29 7:18 ` Andrew Morton 2007-10-29 11:59 ` Kay Sievers 0 siblings, 1 reply; 6+ messages in thread From: Andrew Morton @ 2007-10-29 7:18 UTC (permalink / raw) To: Thomas Meyer; +Cc: Linux Kernel Mailing List, dm-devel, Kay Sievers, Greg KH On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <thomas@m3y3r.de> 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/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 set > CONFIG_BLK_DEV_DM=y > # CONFIG_DM_DEBUG is not set > CONFIG_DM_CRYPT=y > CONFIG_DM_SNAPSHOT=m > CONFIG_DM_MIRROR=m > CONFIG_DM_ZERO=m > # CONFIG_DM_MULTIPATH is not set > CONFIG_DM_DELAY=m > CONFIG_DM_UEVENT=y > # CONFIG_FUSION is not set > > 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? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 2007-10-29 7:18 ` Andrew Morton @ 2007-10-29 11:59 ` Kay Sievers 2007-11-02 17:03 ` Thomas Meyer 0 siblings, 1 reply; 6+ messages in thread From: Kay Sievers @ 2007-10-29 11:59 UTC (permalink / raw) To: Andrew Morton; +Cc: Thomas Meyer, Linux Kernel Mailing List, dm-devel, Greg KH On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote: > On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <thomas@m3y3r.de> 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/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 set > > CONFIG_BLK_DEV_DM=y > > # CONFIG_DM_DEBUG is not set > > CONFIG_DM_CRYPT=y > > CONFIG_DM_SNAPSHOT=m > > CONFIG_DM_MIRROR=m > > CONFIG_DM_ZERO=m > > # CONFIG_DM_MULTIPATH is not set > > CONFIG_DM_DELAY=m > > CONFIG_DM_UEVENT=y > > # CONFIG_FUSION is not set > > > > 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. > 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 2007-10-29 11:59 ` Kay Sievers @ 2007-11-02 17:03 ` Thomas Meyer 2007-11-02 17:12 ` Kay Sievers 0 siblings, 1 reply; 6+ messages in thread From: Thomas Meyer @ 2007-11-02 17:03 UTC (permalink / raw) To: Kay Sievers; +Cc: Andrew Morton, Linux Kernel Mailing List, dm-devel, Greg KH Kay Sievers schrieb: > On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote: > >> On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <thomas@m3y3r.de> 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/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 set >>> CONFIG_BLK_DEV_DM=y >>> # CONFIG_DM_DEBUG is not set >>> CONFIG_DM_CRYPT=y >>> CONFIG_DM_SNAPSHOT=m >>> CONFIG_DM_MIRROR=m >>> CONFIG_DM_ZERO=m >>> # CONFIG_DM_MULTIPATH is not set >>> CONFIG_DM_DELAY=m >>> CONFIG_DM_UEVENT=y >>> # CONFIG_FUSION is not set >>> >>> 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. > > >> 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. > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 2007-11-02 17:03 ` Thomas Meyer @ 2007-11-02 17:12 ` Kay Sievers 2007-11-27 17:06 ` Thomas Meyer 0 siblings, 1 reply; 6+ messages in thread From: Kay Sievers @ 2007-11-02 17:12 UTC (permalink / raw) To: Thomas Meyer; +Cc: Andrew Morton, Linux Kernel Mailing List, dm-devel, Greg KH On Fri, 2007-11-02 at 18:03 +0100, Thomas Meyer wrote: > Kay Sievers schrieb: > > On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote: > > > >> On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <thomas@m3y3r.de> 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/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 set > >>> CONFIG_BLK_DEV_DM=y > >>> # CONFIG_DM_DEBUG is not set > >>> CONFIG_DM_CRYPT=y > >>> CONFIG_DM_SNAPSHOT=m > >>> CONFIG_DM_MIRROR=m > >>> CONFIG_DM_ZERO=m > >>> # CONFIG_DM_MULTIPATH is not set > >>> CONFIG_DM_DELAY=m > >>> CONFIG_DM_UEVENT=y > >>> # CONFIG_FUSION is not set > >>> > >>> 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. > > > >> 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. > > > 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. 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 2007-11-02 17:12 ` Kay Sievers @ 2007-11-27 17:06 ` Thomas Meyer 0 siblings, 0 replies; 6+ messages in thread From: Thomas Meyer @ 2007-11-27 17:06 UTC (permalink / raw) To: Kay Sievers; +Cc: Andrew Morton, Linux Kernel Mailing List, dm-devel, Greg KH Kay Sievers schrieb: > On Fri, 2007-11-02 at 18:03 +0100, Thomas Meyer wrote: > >> Kay Sievers schrieb: >> >>> On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote: >>> >>> >>>> On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <thomas@m3y3r.de> 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/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 set >>>>> CONFIG_BLK_DEV_DM=y >>>>> # CONFIG_DM_DEBUG is not set >>>>> CONFIG_DM_CRYPT=y >>>>> CONFIG_DM_SNAPSHOT=m >>>>> CONFIG_DM_MIRROR=m >>>>> CONFIG_DM_ZERO=m >>>>> # CONFIG_DM_MULTIPATH is not set >>>>> CONFIG_DM_DELAY=m >>>>> CONFIG_DM_UEVENT=y >>>>> # CONFIG_FUSION is not set >>>>> >>>>> 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. >>> >>> >>>> 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. >>> >>> >> 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. >> > > 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. > > Yes. With hal-0.5.10 (which includes above commit) the new kernel behaves like 2.6.23 again. mfg thomas ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-11-27 17:06 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-10-21 19:23 Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0 Thomas Meyer 2007-10-29 7:18 ` Andrew Morton 2007-10-29 11:59 ` Kay Sievers 2007-11-02 17:03 ` Thomas Meyer 2007-11-02 17:12 ` Kay Sievers 2007-11-27 17:06 ` Thomas Meyer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox