From: Chris Mason <clm@fb.com>
To: "hugo@carfax.org.uk" <hugo@carfax.org.uk>
Cc: "wangsl.fnst@cn.fujitsu.com" <wangsl.fnst@cn.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"sbehrens@giantdisaster.de" <sbehrens@giantdisaster.de>
Subject: Re: [PATCH] Btrfs-progs: make send/receive compatible with older kernels
Date: Thu, 9 Jan 2014 14:52:27 +0000 [thread overview]
Message-ID: <1389279172.23310.50.camel@ret.masoncoding.com> (raw)
In-Reply-To: <20140109121606.GI15634@carfax.org.uk>
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 <ablock84@googlemail.com>
> > > Signed-off-by: Wang Shilong <wangsl.fnst@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
next prev parent reply other threads:[~2014-01-09 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 10:52 [PATCH] Btrfs-progs: make send/receive compatible with older kernels Wang Shilong
2014-01-09 11:49 ` Stefan Behrens
2014-01-09 11:56 ` Wang Shilong
2014-01-09 12:16 ` Hugo Mills
2014-01-09 14:52 ` Chris Mason [this message]
2014-01-14 15:27 ` David Sterba
2014-01-18 5:30 ` Wang Shilong
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=1389279172.23310.50.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=wangsl.fnst@cn.fujitsu.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 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.