dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: Matt Coleman <mcoleman@dattobackup.com>
Cc: dm-devel@redhat.com, breeves@redhat.com
Subject: Re: dm-loop and kernel 3.x
Date: Wed, 08 Aug 2012 15:42:27 +0100	[thread overview]
Message-ID: <50227AD3.6040600@redhat.com> (raw)
In-Reply-To: <FB767254-0A6B-42BF-92C7-0527F5329F84@dattobackup.com>

On 08/08/2012 03:33 PM, Matt Coleman wrote:
> I just tried (unsuccessfully) to apply the dm-loop patches to kernel
> 3.2.0. dm-bio-list-helpers.patch failed to apply because
> dm-bio-list.h no longer exists in the kernel tree. Is this an
> abandoned project, or were the changes incorporated into the kernel's
> existing loopback support? (...as hinted at here:
> http://www.redhat.com/archives/dm-devel/2012-February/msg00041.html)

Most of the support patches went in to mainline several years ago so
this is probably due to later changes in md/ - I'd have to take a look
at the errors to see what's failing for you.

That said, the original patch is somewhat abandoned at this stage. I've
not done any work on it beyond helping folks get it applied and built
for quite a few years and the block mapping approach it uses was
rejected on LKML without VFS changes to make it safe (it operates behind
the file system's back).

I did start work last year on a revised dm-loop that was a refactoring
of and thin wrapper around the existing drivers/block loop driver but
this isn't published anywhere at the moment.

It could probably be cleaned up and put somewhere without too much work
but it's not something I'm working on regularly at the moment.

I know Mikulas was also interested in reviving dm-loop and we had some
discussions at Devconf in Brno earlier in the year but nothing has
happened since.

Regards,
Bryn.

  reply	other threads:[~2012-08-08 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 14:33 dm-loop and kernel 3.x Matt Coleman
2012-08-08 14:42 ` Bryn M. Reeves [this message]
2012-08-08 14:46 ` Bryn M. Reeves
2012-08-08 15:34   ` Matt Coleman
2012-08-08 16:00     ` Bryn M. Reeves

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=50227AD3.6040600@redhat.com \
    --to=bmr@redhat.com \
    --cc=breeves@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mcoleman@dattobackup.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;
as well as URLs for NNTP newsgroup(s).