From: Cyrill Gorcunov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/2] fiber_wakeup() nop on self
Date: Tue, 27 Apr 2021 00:56:32 +0300 [thread overview]
Message-ID: <YIc3EJROiSONeLVW@grain> (raw)
In-Reply-To: <cover.1619219639.git.v.shpilevoy@tarantool.org>
On Sat, Apr 24, 2021 at 01:15:52AM +0200, Vladislav Shpilevoy wrote:
> The patchset makes fiber_wakeup() in C and fiber.wakeup() in Lua
> nop when called on the current fiber. This fixes a couple of
> crashes in the public API, and prevent spurious wakeups in
> certain cases.
>
> Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-5292-6043-fiber-wakeup-nop
> Issue: https://github.com/tarantool/tarantool/issues/5292
> Issue: https://github.com/tarantool/tarantool/issues/6043
>
> Vladislav Shpilevoy (2):
> fiber: make wakeup in Lua and C nop on self
> fiber: use wakeup safely on self everywhere
Ack
next prev parent reply other threads:[~2021-04-26 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 23:15 Vladislav Shpilevoy via Tarantool-patches
2021-04-23 23:15 ` [Tarantool-patches] [PATCH 1/2] fiber: make wakeup in Lua and C " Vladislav Shpilevoy via Tarantool-patches
2021-04-25 9:21 ` Serge Petrenko via Tarantool-patches
2021-04-25 15:53 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-26 9:21 ` Serge Petrenko via Tarantool-patches
2021-04-23 23:15 ` [Tarantool-patches] [PATCH 2/2] fiber: use wakeup safely on self everywhere Vladislav Shpilevoy via Tarantool-patches
2021-04-25 9:23 ` Serge Petrenko via Tarantool-patches
2021-04-26 21:56 ` Cyrill Gorcunov via Tarantool-patches [this message]
2021-04-27 12:03 ` [Tarantool-patches] [PATCH 0/2] fiber_wakeup() nop on self Kirill Yukhin via Tarantool-patches
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=YIc3EJROiSONeLVW@grain \
--to=tarantool-patches@dev.tarantool.org \
--cc=gorcunov@gmail.com \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 0/2] fiber_wakeup() nop on self' \
/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