linux-kernel - Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 02 Nov 2007 18:03:17 +0100
From:	Thomas Meyer <thomas@...3r.de>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	dm-devel@...hat.com, Greg KH <greg@...ah.com>
Subject: Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0

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@...3r.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.

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