From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Possible severe bug in the device mapper?
Date: Tue, 01 Feb 2011 10:03:16 +0000 [thread overview]
Message-ID: <1296554596.1366.4.camel@ubuntu> (raw)
In-Reply-To: <4D47D29F.5040200@gmx.com>
On Tue, 2011-02-01 at 10:30 +0100, Andreas Heinlein wrote:
> I will continue looking for help, can you point me in some direction?
> 'losetup' is part of util-linux, but I doubt this has actually
> anything
> to do withit. The loopback device code itself is part of the kernel,
> right?
Yes, you should try and find someone who admits to being the loopback
device maintainer and try and have a chat with them. Also it would be
interesting to know how OpenSuse are doing a better job of handling
this. For instance is it a userland solution or have they changed
something in kernel?
- Joe
next prev parent reply other threads:[~2011-02-01 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:30 Possible severe bug in the device mapper? Andreas Heinlein
2011-01-31 11:13 ` Milan Broz
2011-01-31 11:20 ` Joe Thornber
2011-02-01 9:30 ` Andreas Heinlein
2011-02-01 10:03 ` Joe Thornber [this message]
2011-02-01 10:05 ` Zdenek Kabelac
2011-02-01 13:29 ` Andreas Heinlein
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=1296554596.1366.4.camel@ubuntu \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
/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