From: NeilBrown <neilb@suse.com>
To: Sage Weil <sweil@redhat.com>, torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph fixes for -rc7
Date: Fri, 25 Mar 2016 15:02:30 +1100 [thread overview]
Message-ID: <87fuvfw6g9.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <alpine.DEB.2.11.1603052045320.25897@cpach.fuggernut.com>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
On Sun, Mar 06 2016, Sage Weil wrote:
> Hi Linus,
>
> Please pull the following Ceph patch from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
>
> This is a final commit we missed to align the protocol compatibility with
> the feature bits. It decodes a few extra fields in two different messages
> and reports EIO when they are used (not yet supported).
>
> Thanks!
> sage
>
>
> ----------------------------------------------------------------
> Yan, Zheng (1):
> ceph: initial CEPH_FEATURE_FS_FILE_LAYOUT_V2 support
Just wondering, but was CEPH_FEATURE_FS_FILE_LAYOUT_V2 supposed to have
exactly the same value as CEPH_FEATURE_NEW_OSDOPREPLY_ENCODING (and
CEPH_FEATURE_CRUSH_TUNABLES5)??
Because when I backported this patch (and many others) to some ancient
enterprise kernel, it caused mounts to fail. If it really is meant to
be the same value, then I must have some other backported issue to find
and fix.
Thanks,
NeilBrown
>
> fs/ceph/addr.c | 4 ++++
> fs/ceph/caps.c | 27 ++++++++++++++++++++++++---
> fs/ceph/inode.c | 2 ++
> fs/ceph/mds_client.c | 16 ++++++++++++++++
> fs/ceph/mds_client.h | 1 +
> fs/ceph/super.h | 1 +
> include/linux/ceph/ceph_features.h | 1 +
> 7 files changed, 49 insertions(+), 3 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-25 4:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 1:48 Sage Weil
2016-03-25 4:02 ` NeilBrown [this message]
2016-03-25 9:34 ` Ilya Dryomov
2016-03-30 0:24 ` NeilBrown
2016-03-30 2:30 ` Yan, Zheng
2016-03-30 2:40 ` NeilBrown
2016-03-30 8:04 ` Ilya Dryomov
2016-03-30 18:09 ` Gregory Farnum
2016-03-31 2:18 ` NeilBrown
2016-03-28 2:12 ` Yan, Zheng
-- strict thread matches above, loose matches on Subject: below --
2015-01-28 18:55 Sage Weil
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=87fuvfw6g9.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sweil@redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome