linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>, Ilya Dryomov <idryomov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org,
	Dongsheng Yang <dongsheng.yang@easystack.cn>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	linux-block <linux-block@vger.kernel.org>
Subject: Re: [PATCH AUTOSEL 5.3 15/71] rbd: fix response length parameter for encoded strings
Date: Tue, 8 Oct 2019 21:45:18 -0600	[thread overview]
Message-ID: <ecddc946-4fbf-4bb2-aac2-689135473f36@kernel.dk> (raw)
In-Reply-To: <20191008212944.GD1396@sasha-vm>

On 10/8/19 3:29 PM, Sasha Levin wrote:
> On Tue, Oct 01, 2019 at 07:15:49PM +0200, Ilya Dryomov wrote:
>> On Tue, Oct 1, 2019 at 6:39 PM Sasha Levin <sashal@kernel.org> wrote:
>>>
>>> From: Dongsheng Yang <dongsheng.yang@easystack.cn>
>>>
>>> [ Upstream commit 5435d2069503e2aa89c34a94154f4f2fa4a0c9c4 ]
>>>
>>> rbd_dev_image_id() allocates space for length but passes a smaller
>>> value to rbd_obj_method_sync().  rbd_dev_v2_object_prefix() doesn't
>>> allocate space for length.  Fix both to be consistent.
>>>
>>> Signed-off-by: Dongsheng Yang <dongsheng.yang@easystack.cn>
>>> Reviewed-by: Ilya Dryomov <idryomov@gmail.com>
>>> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
>>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>>> ---
>>>   drivers/block/rbd.c | 10 ++++++----
>>>   1 file changed, 6 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
>>> index c8fb886aebd4e..69db7385c8df5 100644
>>> --- a/drivers/block/rbd.c
>>> +++ b/drivers/block/rbd.c
>>> @@ -5669,17 +5669,20 @@ static int rbd_dev_v2_image_size(struct rbd_device *rbd_dev)
>>>
>>>   static int rbd_dev_v2_object_prefix(struct rbd_device *rbd_dev)
>>>   {
>>> +       size_t size;
>>>          void *reply_buf;
>>>          int ret;
>>>          void *p;
>>>
>>> -       reply_buf = kzalloc(RBD_OBJ_PREFIX_LEN_MAX, GFP_KERNEL);
>>> +       /* Response will be an encoded string, which includes a length */
>>> +       size = sizeof(__le32) + RBD_OBJ_PREFIX_LEN_MAX;
>>> +       reply_buf = kzalloc(size, GFP_KERNEL);
>>>          if (!reply_buf)
>>>                  return -ENOMEM;
>>>
>>>          ret = rbd_obj_method_sync(rbd_dev, &rbd_dev->header_oid,
>>>                                    &rbd_dev->header_oloc, "get_object_prefix",
>>> -                                 NULL, 0, reply_buf, RBD_OBJ_PREFIX_LEN_MAX);
>>> +                                 NULL, 0, reply_buf, size);
>>>          dout("%s: rbd_obj_method_sync returned %d\n", __func__, ret);
>>>          if (ret < 0)
>>>                  goto out;
>>> @@ -6696,7 +6699,6 @@ static int rbd_dev_image_id(struct rbd_device *rbd_dev)
>>>          dout("rbd id object name is %s\n", oid.name);
>>>
>>>          /* Response will be an encoded string, which includes a length */
>>> -
>>>          size = sizeof (__le32) + RBD_IMAGE_ID_LEN_MAX;
>>>          response = kzalloc(size, GFP_NOIO);
>>>          if (!response) {
>>> @@ -6708,7 +6710,7 @@ static int rbd_dev_image_id(struct rbd_device *rbd_dev)
>>>
>>>          ret = rbd_obj_method_sync(rbd_dev, &oid, &rbd_dev->header_oloc,
>>>                                    "get_id", NULL, 0,
>>> -                                 response, RBD_IMAGE_ID_LEN_MAX);
>>> +                                 response, size);
>>>          dout("%s: rbd_obj_method_sync returned %d\n", __func__, ret);
>>>          if (ret == -ENOENT) {
>>>                  image_id = kstrdup("", GFP_KERNEL);
>>
>> Hi Sasha,
>>
>> This patch just made things consistent, there was no bug here.  I don't
>> think it should be backported.
> 
> I'll drop it, thanks!

How did it even get picked up, it's not marked for stable?

-- 
Jens Axboe


  reply	other threads:[~2019-10-09  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191001163922.14735-1-sashal@kernel.org>
2019-10-01 16:38 ` [PATCH AUTOSEL 5.3 15/71] rbd: fix response length parameter for encoded strings Sasha Levin
2019-10-01 17:15   ` Ilya Dryomov
2019-10-08 21:29     ` Sasha Levin
2019-10-09  3:45       ` Jens Axboe [this message]
2019-10-01 16:39 ` [PATCH AUTOSEL 5.3 54/71] blk-mq: move lockdep_assert_held() into elevator_exit Sasha Levin

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=ecddc946-4fbf-4bb2-aac2-689135473f36@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dongsheng.yang@easystack.cn \
    --cc=idryomov@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).