From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@dev.tarantool.org, kostja.osipov@gmail.com Subject: Re: [Tarantool-patches] [PATCH v3 1/1] iproto: don't destroy a session during disconnect Date: Fri, 22 Nov 2019 00:04:51 +0100 [thread overview] Message-ID: <a144f069-c4aa-cdc3-fd5c-a1b7cd963aca@tarantool.org> (raw) In-Reply-To: <4c563cef125a2b96a3379defc40fdae4c2a0bc6d.1574112599.git.v.shpilevoy@tarantool.org> I forgot to push a test file. Here it is. ================================================================================ diff --git a/test/box/gh-4627-session-use-after-free.result b/test/box/gh-4627-session-use-after-free.result new file mode 100644 index 000000000..5e5c154b9 --- /dev/null +++ b/test/box/gh-4627-session-use-after-free.result @@ -0,0 +1,60 @@ +-- test-run result file version 2 +-- +-- gh-4627: 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. +-- +net_box = require('net.box') + | --- + | ... +fiber = require('fiber') + | --- + | ... + +sid_before_yield = nil + | --- + | ... +sid_after_yield = nil + | --- + | ... +func = box.session.on_disconnect(function() \ + sid_before_yield = box.session.id() \ + fiber.yield() \ + sid_after_yield = box.session.id() \ +end) + | --- + | ... + +connection = net_box.connect(box.cfg.listen) + | --- + | ... +connection:ping() + | --- + | - true + | ... +connection:close() + | --- + | ... + +while not sid_after_yield do fiber.yield() end + | --- + | ... + +sid_after_yield == sid_before_yield and sid_after_yield ~= 0 or \ + {sid_after_yield, sid_before_yield} + | --- + | - true + | ... + +box.session.on_disconnect(nil, func) + | --- + | ... diff --git a/test/box/gh-4627-session-use-after-free.test.lua b/test/box/gh-4627-session-use-after-free.test.lua new file mode 100644 index 000000000..70624a96a --- /dev/null +++ b/test/box/gh-4627-session-use-after-free.test.lua @@ -0,0 +1,35 @@ +-- +-- gh-4627: 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. +-- +net_box = require('net.box') +fiber = require('fiber') + +sid_before_yield = nil +sid_after_yield = nil +func = box.session.on_disconnect(function() \ + sid_before_yield = box.session.id() \ + fiber.yield() \ + sid_after_yield = box.session.id() \ +end) + +connection = net_box.connect(box.cfg.listen) +connection:ping() +connection:close() + +while not sid_after_yield do fiber.yield() end + +sid_after_yield == sid_before_yield and sid_after_yield ~= 0 or \ + {sid_after_yield, sid_before_yield} + +box.session.on_disconnect(nil, func)
next prev parent reply other threads:[~2019-11-21 22:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-18 21:31 Vladislav Shpilevoy 2019-11-19 7:27 ` Konstantin Osipov 2019-11-21 23:04 ` Vladislav Shpilevoy [this message] 2019-11-22 7:55 ` Konstantin Osipov 2019-11-26 7:51 ` Kirill Yukhin
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=a144f069-c4aa-cdc3-fd5c-a1b7cd963aca@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=kostja.osipov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 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