On Thu, 2014-01-09 at 12:16 +0000, Hugo Mills wrote:
> On Thu, Jan 09, 2014 at 12:49:48PM +0100, Stefan Behrens wrote:
> > On Thu, 9 Jan 2014 18:52:38 +0800, Wang Shilong wrote:
> > > Some users complaint that with latest btrfs-progs, they will
> > > fail to use send/receive. The problem is new tool will try
> > > to use uuid tree while it dosen't work on older kernel.
> > >
> > > Now we first check if we support uuid tree, if not we fall into
> > > normal search as previous way.i copy most of codes from Alexander
> > > Block's previous codes and did some adjustments to make it work.
> > >
> > > Signed-off-by: Alexander Block <abloc...@googlemail.com>
> > > Signed-off-by: Wang Shilong <wangsl.f...@cn.fujitsu.com>
> > > ---
> > > send-utils.c | 352
> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > > send-utils.h | 11 ++
> > > 2 files changed, 359 insertions(+), 4 deletions(-)
> >
> > I'd prefer a printf("Needs kernel 3.12 or better\n") if no UUID tree is
> > found. The code that you add will never be tested by anyone and will
> > become broken sooner or later.
> >
> > The new kernel is compatible to old progs and to new progs. But new
> > progs require a new kernel and IMO this is normal.
>
> No. Really, no. I think I would be extremely upset to upgrade, say,
> util-linux, only to discover that I needed a new kernel for cp to
> continue to work. I hope you would be, too.
>
> You may need to upgrade the kernel to get new features offered by a
> new userspace, but I think we should absolutely not be changing
> userspace in a way that makes it incompatible with older kernels.
I'd really prefer that we maintain compatibility with the older kernels.
Heavy btrfs usage is going to want a newer kernel anyway, but this is an
important policy to keep in place for the future.
Especially since Wang went to the trouble of making the patch, I'd
rather take it.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
