From: Milan Broz <mbroz@redhat.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>
Subject: Re: [PATCH] Re: Oops using 2.6.28.n after a lazy umount of a crypted loop-device
Date: Fri, 06 Mar 2009 09:24:54 +0100 [thread overview]
Message-ID: <49B0DDD6.2080608@redhat.com> (raw)
In-Reply-To: <49B0BFBD.7060208@ahsoftware.de>
Alexander Holler wrote:
> Milan Broz schrieb:
>> Please Can you try attached patch if helps here?
>> (Patch is not perfect, but should help, at least identify that
>> it is the same problem I am fixing:-)
>
> The patch works (I had to add an #include <linux/delay.h> /* msleep */).
ok, thanks.
> I've tested it using 2.6.28.7 and the script below. With your patch the
> script was running over night looping about 400 times without any error.
> A crosscheck without the patch needed only 10 iterations to get an oops.
> So I assume you have fixed the problem I had. ;)
>
> There stills seems to be another problem left, I've got 3 times the
> kernel-message
>
> device-mapper: ioctl: unable to remove open device
> temporary-cryptsetup-21571
This is bug in cryptsetup related to udev (udev should not touch temporary
cryptsetup device) which is fixed upstream, but there is no
new release yet (Fedora has this patched, not sure about other distros)
see http://code.google.com/p/cryptsetup/source/detail?r=32 and other patches.
Milan
--
mbroz@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <mbroz@redhat.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] Re: Oops using 2.6.28.n after a lazy umount of a crypted loop-device
Date: Fri, 06 Mar 2009 09:24:54 +0100 [thread overview]
Message-ID: <49B0DDD6.2080608@redhat.com> (raw)
In-Reply-To: <49B0BFBD.7060208@ahsoftware.de>
Alexander Holler wrote:
> Milan Broz schrieb:
>> Please Can you try attached patch if helps here?
>> (Patch is not perfect, but should help, at least identify that
>> it is the same problem I am fixing:-)
>
> The patch works (I had to add an #include <linux/delay.h> /* msleep */).
ok, thanks.
> I've tested it using 2.6.28.7 and the script below. With your patch the
> script was running over night looping about 400 times without any error.
> A crosscheck without the patch needed only 10 iterations to get an oops.
> So I assume you have fixed the problem I had. ;)
>
> There stills seems to be another problem left, I've got 3 times the
> kernel-message
>
> device-mapper: ioctl: unable to remove open device
> temporary-cryptsetup-21571
This is bug in cryptsetup related to udev (udev should not touch temporary
cryptsetup device) which is fixed upstream, but there is no
new release yet (Fedora has this patched, not sure about other distros)
see http://code.google.com/p/cryptsetup/source/detail?r=32 and other patches.
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-03-06 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 10:11 Oops using 2.6.28.n after a lazy umount of a crypted loop-device Alexander Holler
2009-03-05 11:58 ` [PATCH] " Milan Broz
2009-03-05 11:58 ` Milan Broz
2009-03-06 6:16 ` Alexander Holler
2009-03-06 8:24 ` Milan Broz [this message]
2009-03-06 8:24 ` Milan Broz
2009-03-12 11:51 ` [PATCH] dm crypt: wait for possible unfinished endio() call in destructor Milan Broz
2009-03-13 13:53 ` Alasdair G Kergon
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=49B0DDD6.2080608@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.