From: xiubli@redhat.com
To: ceph-devel@vger.kernel.org
Cc: idryomov@gmail.com, jlayton@kernel.org, vshankar@redhat.com,
mchangir@redhat.com, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v3 0/2] libceph: sparse-read misc fixes
Date: Mon, 6 Nov 2023 09:16:42 +0800 [thread overview]
Message-ID: <20231106011644.248119-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
V3:
- Remove the WARN_ON_ONCE().
- Return -EREMOTEIO when the datalen and extents mismatch.
V2:
- Remove [1/3] patch from V1.
Xiubo Li (2):
libceph: save and covert sr_datalen to host-endian
libceph: check the data length when sparse-read finishes
include/linux/ceph/osd_client.h | 3 ++-
net/ceph/osd_client.c | 15 ++++++++++++++-
2 files changed, 16 insertions(+), 2 deletions(-)
--
2.39.1
next reply other threads:[~2023-11-06 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 1:16 xiubli [this message]
2023-11-06 1:16 ` [PATCH v3 1/2] libceph: save and covert sr_datalen to host-endian xiubli
2023-11-06 1:16 ` [PATCH v3 2/2] libceph: check the data length when sparse-read finishes xiubli
2023-11-06 11:54 ` Ilya Dryomov
2023-11-06 12:17 ` Xiubo Li
2023-11-06 12:32 ` Jeff Layton
2023-11-06 13:01 ` Xiubo Li
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=20231106011644.248119-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=mchangir@redhat.com \
--cc=vshankar@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).