From: Andrew Morton <akpm@osdl.org>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: torvalds@osdl.org, agk@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] Device-mapper snapshot metadata userspace breakage
Date: Thu, 20 Apr 2006 03:10:13 -0700 [thread overview]
Message-ID: <20060420031013.68cff2cf.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0604201302090.29821@sbz-30.cs.Helsinki.FI>
Pekka J Enberg <penberg@cs.Helsinki.FI> wrote:
>
> Hi Andrew,
>
> Pekka J Enberg <penberg@cs.Helsinki.FI> wrote:
> > > The commit aa14edeb994f8f7e223d02ad14780bf2fa719f6d "[PATCH] device-mapper
> > > snapshot: load metadata on creation" breaks userspace and is blocking us
> > > from moving to the 2.6.16 series kernel. Debian doesn't have the
> > > new required LVM version in stable yet. Is the change intentional?
>
> On Thu, 20 Apr 2006, Andrew Morton wrote:
> > The changelog said
> >
> > If you're using lvm2, for this patch to work properly you should update
> > to lvm2 version 2.02.01 or later and device-mapper version 1.02.02 or
> > later.
> >
> > Which was pretty bad of us. I hope LVM 2.02.01 userspace is
> > back-compatible with older kernels?
>
> Yeah, I know, but that still leaves us in an unfortunate situation as the
> 2.6.16 series has security fixes that are not AFAIK in 2.6.15. Anyway, if
> the change is intentional and approved, I guess we'll just have to live
> with it. Thanks!
>
Well I wouldn't say it was "approved". It was disapproved of and
grudgingly accepted :(
More info here: http://lkml.org/lkml/2006/1/23/130
next prev parent reply other threads:[~2006-04-20 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 9:53 [PROBLEM] Device-mapper snapshot metadata userspace breakage Pekka J Enberg
2006-04-20 9:59 ` Andrew Morton
2006-04-20 10:04 ` Pekka J Enberg
2006-04-20 10:10 ` Andrew Morton [this message]
2006-04-20 10:08 ` Juergen Kreileder
2006-04-20 17:37 ` Alasdair G Kergon
2006-04-21 6:41 ` Pekka J Enberg
2006-04-21 15:17 ` Juergen Kreileder
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=20060420031013.68cff2cf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
--cc=torvalds@osdl.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.