From: Maksim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, sergeyb@tarantool.org, skaplun@tarantool.org, m.kokryashkin@tarantool.org Subject: [Tarantool-patches] [PATCH luajit 2/2] Fix last commit. Date: Fri, 27 Oct 2023 15:57:38 +0300 [thread overview] Message-ID: <20231027125738.29527-3-max.kokryashkin@gmail.com> (raw) In-Reply-To: <20231027125738.29527-1-max.kokryashkin@gmail.com> From: Mike Pall <mike> Reported by PluMGMK. (cherry-picked from commit 224129a8e64bfa219d35cd03055bf03952f167f6) The error handler for GC finalizers was not cleared from the stack after the initialization. This commit adds stack cleanup. Maxim Kokryashkin: * added the description and the test for the problem Part of tarantool/tarantool#9145 --- src/lib_aux.c | 2 ++ .../fix-finalizer-error-handler-init.test.c | 30 +++++++++++++++++++ 2 files changed, 32 insertions(+) create mode 100644 test/tarantool-c-tests/fix-finalizer-error-handler-init.test.c diff --git a/src/lib_aux.c b/src/lib_aux.c index d532a12f..ecdc67f9 100644 --- a/src/lib_aux.c +++ b/src/lib_aux.c @@ -352,6 +352,7 @@ LUALIB_API lua_State *luaL_newstate(void) lua_pushcfunction(L, error_finalizer); lua_rawseti(L, -2, VMEVENT_HASH(LJ_VMEVENT_ERRFIN)); G(L)->vmevmask = VMEVENT_MASK(LJ_VMEVENT_ERRFIN); + L->top--; #endif } return L; @@ -378,6 +379,7 @@ LUALIB_API lua_State *luaL_newstate(void) lua_pushcfunction(L, error_finalizer); lua_rawseti(L, -2, VMEVENT_HASH(LJ_VMEVENT_ERRFIN)); G(L)->vmevmask = VMEVENT_MASK(LJ_VMEVENT_ERRFIN); + L->top--; #endif } return L; diff --git a/test/tarantool-c-tests/fix-finalizer-error-handler-init.test.c b/test/tarantool-c-tests/fix-finalizer-error-handler-init.test.c new file mode 100644 index 00000000..44c1d96b --- /dev/null +++ b/test/tarantool-c-tests/fix-finalizer-error-handler-init.test.c @@ -0,0 +1,30 @@ +#include "lua.h" +#include "test.h" +#include "utils.h" + +#include "lj_obj.h" + +/* + * This test demonstrates an uncleared Lua stack after the + * initialization of the error handler for GC finalizers. + */ + +static int stack_is_clean(void *test_state) +{ + lua_State *L = test_state; + assert_ptr_equal(L->top, L->base); + return TEST_EXIT_SUCCESS; +} + +int main(void) +{ + lua_State *L = utils_lua_init(); + + const struct test_unit tgroup[] = { + test_unit_def(stack_is_clean) + }; + + const int test_result = test_run_group(tgroup, L); + utils_lua_close(L); + return test_result; +} -- 2.39.3 (Apple Git-145)
next prev parent reply other threads:[~2023-10-27 12:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-27 12:57 [Tarantool-patches] [PATCH luajit 0/2] gc: handle errors in finalizers Maksim Kokryashkin via Tarantool-patches 2023-10-27 12:57 ` [Tarantool-patches] [PATCH luajit 1/2] Print errors from __gc finalizers instead of rethrowing them Maksim Kokryashkin via Tarantool-patches 2023-11-01 8:15 ` Sergey Kaplun via Tarantool-patches 2023-10-27 12:57 ` Maksim Kokryashkin via Tarantool-patches [this message] 2023-11-01 8:56 ` [Tarantool-patches] [PATCH luajit 2/2] Fix last commit Sergey Kaplun 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=20231027125738.29527-3-max.kokryashkin@gmail.com \ --to=tarantool-patches@dev.tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --cc=max.kokryashkin@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 2/2] Fix last commit.' \ /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