From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] iproto: don't destroy a session during disconnect
Date: Sat, 16 Nov 2019 14:54:21 +0300 [thread overview]
Message-ID: <20191116115421.GD14490@atlas> (raw)
In-Reply-To: <0e1af790a8cbc380fcd3bb7c7295f5f5b80d98a3.1573862438.git.v.shpilevoy@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/11/16 12:48]:
> Binary session disconnect trigger yield could lead to use after
> free of the session object. That happened because iproto thread
> sent two requests to TX thread at disconnect:
>
> - Close the session and run its on disconnect triggers;
>
> - If all requests are handled, destroy the session.
>
> When a connection is idle, all requests are handled, so both these
> requests are sent. If the first one yielded in TX thread, the
> second one arrived and destroyed the session right under the feet
> of the first one.
>
> This can be solved in two ways - in TX thread, and in iproto
> thread.
>
> TX thread solution (which is chosen in the patch): add a flag
> which says whether disconnect is processed by TX. When destroy
> request arrives, it checks the flag. If disconnect is not done,
> the destroy request waits on a condition variable until it is.
>
> The solution is simple, but adds new members to iproto_connection
> struct, and requires lots of commenting.
>
> Iproto thread solution (alternative): just don't send destroy
> request until disconnect returns back to iproto thread.
I like this one more to be honest.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-11-16 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:02 Vladislav Shpilevoy
2019-11-16 11:54 ` Konstantin Osipov [this message]
2019-11-16 12:25 ` Vladislav Shpilevoy
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=20191116115421.GD14490@atlas \
--to=kostja.osipov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 1/1] iproto: don'\''t destroy a session during disconnect' \
/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