public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dm-devel@redhat.com, Kay Sievers <kay.sievers@vrfy.org>,
	Greg KH <greg@kroah.com>
Subject: Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0
Date: Mon, 29 Oct 2007 00:18:32 -0700	[thread overview]
Message-ID: <20071029001832.05c0a372.akpm@linux-foundation.org> (raw)
In-Reply-To: <471BA729.6050206@m3y3r.de>

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?


  reply	other threads:[~2007-10-29  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071029001832.05c0a372.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox