From: David Disseldorp <ddiss@suse.de>
To: Jeff Layton <jlayton@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, "Yan, Zheng" <zyan@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/4] ceph: endianness fixes and sparse warning fixes
Date: Tue, 17 Jan 2017 19:26:05 +0100 [thread overview]
Message-ID: <20170117192605.144022a7@suse.de> (raw)
In-Reply-To: <1484310965.2616.7.camel@redhat.com>
On Fri, 13 Jan 2017 07:36:05 -0500, Jeff Layton wrote:
> Thanks. Should we send this series to stable? I'm not sure how common
> kcephfs mounts are on BE arches, but these bugs would likely prevent it
> from working.
Please do, Jeff. I hit the [PATCH 4/4] bug on first CephFS I/O with
s390x (BE):
[ 2691.805255] ceph: mds parse_reply err -5
[ 2691.805256] ceph: mdsc_handle_reply got corrupt reply mds0(tid:5)
Cheers, David
next prev parent reply other threads:[~2017-01-17 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:12 [PATCH 0/4] ceph: endianness fixes and sparse warning fixes Jeff Layton
2017-01-12 16:12 ` [PATCH 1/4] ceph: fix endianness of getattr mask in ceph_d_revalidate Jeff Layton
2017-01-12 16:43 ` Ilya Dryomov
2017-01-12 17:16 ` Jeff Layton
2017-01-12 16:12 ` [PATCH 2/4] ceph: fix endianness bug in frag_tree_split_cmp Jeff Layton
2017-01-12 16:12 ` [PATCH 3/4] ceph: fix bogus endianness change in ceph_ioctl_set_layout Jeff Layton
2017-01-12 16:12 ` [PATCH 4/4] ceph: fix bad endianness handling in parse_reply_info_extra Jeff Layton
2017-01-12 16:23 ` [PATCH 0/4] ceph: endianness fixes and sparse warning fixes Sage Weil
2017-01-13 12:36 ` Jeff Layton
2017-01-17 18:26 ` David Disseldorp [this message]
2017-01-17 18:28 ` Ilya Dryomov
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=20170117192605.144022a7@suse.de \
--to=ddiss@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@redhat.com \
--cc=sweil@redhat.com \
--cc=zyan@redhat.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