From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
Subject: [tarantool-patches] Re: [PATCH 1/1] fiber: extend name buffer on 1 byte for \0
Date: Sun, 24 Feb 2019 14:07:18 +0300 [thread overview]
Message-ID: <0b29a753-83bf-0f3a-d8c9-5418fdd66c43@tarantool.org> (raw)
In-Reply-To: <08ce04d1843cfd15d255608d8ec7eaf70f804e9e.1551005861.git.v.shpilevoy@tarantool.org>
Pushed to 2.1, 1.10 as obvious.
On 24/02/2019 13:58, Vladislav Shpilevoy wrote:
> Checks for fiber_name legth worked with FIBER_NAME_MAX,
> while one byte in fact was occupied by terminating zero.
>
> Closes #4011
> ---
> Issue: https://github.com/tarantool/tarantool/issues/4011
>
> src/fiber.h | 2 +-
> test/app/fiber.result | 8 ++++----
> test/app/fiber.test.lua | 2 +-
> test/unit/fiber.result | 2 +-
> 4 files changed, 7 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2019-02-24 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 10:58 [tarantool-patches] " Vladislav Shpilevoy
2019-02-24 11:07 ` Vladislav Shpilevoy [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=0b29a753-83bf-0f3a-d8c9-5418fdd66c43@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/1] fiber: extend name buffer on 1 byte for \0' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox