From: Josh Durgin <jdurgin@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] crush: fix a bug in tree bucket decode
Date: Tue, 30 Jun 2015 09:09:52 -0700 [thread overview]
Message-ID: <5592BF50.3030504@redhat.com> (raw)
In-Reply-To: <1435598272-44621-1-git-send-email-idryomov@gmail.com>
On 06/29/2015 10:17 AM, Ilya Dryomov wrote:
> struct crush_bucket_tree::num_nodes is u8, so ceph_decode_8_safe()
> should be used. -Wconversion catches this, but I guess it went
> unnoticed in all the noise it spews. The actual problem (at least for
> common crushmaps) isn't the u32 -> u8 truncation though - it's the
> advancement by 4 bytes insead of 1 in the crushmap buffer.
>
> Fixes: http://tracker.ceph.com/issues/2759
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
> ---
> net/ceph/osdmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ceph/osdmap.c b/net/ceph/osdmap.c
> index 15796696d64e..4a3125836b64 100644
> --- a/net/ceph/osdmap.c
> +++ b/net/ceph/osdmap.c
> @@ -89,7 +89,7 @@ static int crush_decode_tree_bucket(void **p, void *end,
> {
> int j;
> dout("crush_decode_tree_bucket %p to %p\n", *p, end);
> - ceph_decode_32_safe(p, end, b->num_nodes, bad);
> + ceph_decode_8_safe(p, end, b->num_nodes, bad);
> b->node_weights = kcalloc(b->num_nodes, sizeof(u32), GFP_NOFS);
> if (b->node_weights == NULL)
> return -ENOMEM;
>
Reviewed-by: Josh Durgin <jdurgin@redhat.com>
prev parent reply other threads:[~2015-06-30 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 17:17 [PATCH] crush: fix a bug in tree bucket decode Ilya Dryomov
2015-06-30 16:09 ` Josh Durgin [this message]
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=5592BF50.3030504@redhat.com \
--to=jdurgin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.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.