From: "Luís Henriques" <lhenriques@suse.de>
To: Xiubo Li <xiubli@redhat.com>
Cc: jlayton@kernel.org, idryomov@gmail.com, vshankar@redhat.com,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: fix incorrectly assigning random values to peer's members
Date: Mon, 06 Jun 2022 11:13:01 +0100 [thread overview]
Message-ID: <87ee022j82.fsf@brahms.olymp> (raw)
In-Reply-To: <20220606072835.302935-1-xiubli@redhat.com> (Xiubo Li's message of "Mon, 6 Jun 2022 15:28:35 +0800")
Xiubo Li <xiubli@redhat.com> writes:
> For export the peer is empty in ceph.
>
> URL: https://tracker.ceph.com/issues/55857
> Signed-off-by: Xiubo Li <xiubli@redhat.com>
> ---
> fs/ceph/caps.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
> index 0a48bf829671..8efa46ff4282 100644
> --- a/fs/ceph/caps.c
> +++ b/fs/ceph/caps.c
> @@ -4127,16 +4127,11 @@ void ceph_handle_caps(struct ceph_mds_session *session,
> p += flock_len;
> }
>
> - if (msg_version >= 3) {
> - if (op == CEPH_CAP_OP_IMPORT) {
> - if (p + sizeof(*peer) > end)
> - goto bad;
> - peer = p;
> - p += sizeof(*peer);
> - } else if (op == CEPH_CAP_OP_EXPORT) {
> - /* recorded in unused fields */
> - peer = (void *)&h->size;
> - }
> + if (msg_version >= 3 && op == CEPH_CAP_OP_IMPORT) {
> + if (p + sizeof(*peer) > end)
> + goto bad;
> + peer = p;
> + p += sizeof(*peer);
> }
>
> if (msg_version >= 4) {
> --
>
> 2.36.0.rc1
>
Are you sure this isn't breaking anything? Looking at MClientCaps.h, it
seems to be doing something similar, i.e. for the CAP_OP_EXPORT, the
'peer' is encoded where the 'size', 'max_size', 'truncate_size',... are
for the CAP_OP_IMPORT. This is definitely confusing and messy, but not
sure if your change isn't breaking something.
Cheers,
--
Luís
next prev parent reply other threads:[~2022-06-06 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 7:28 [PATCH] ceph: fix incorrectly assigning random values to peer's members Xiubo Li
2022-06-06 10:13 ` Luís Henriques [this message]
2022-06-06 10:23 ` Jeff Layton
2022-06-06 11:48 ` 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=87ee022j82.fsf@brahms.olymp \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=vshankar@redhat.com \
--cc=xiubli@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 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.