From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH luajit 0/2] VM events and finalizers in separate state
Date: Sat, 28 Mar 2026 18:31:15 +0300 [thread overview]
Message-ID: <cover.1774711616.git.skaplun@tarantool.org> (raw)
This patchset fixes the corner case of VM event stack overflow, which
results in broken JIT recording. The second patch is a fixup for the
first one.
Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-1403-vmevent-crash-on-stkov
Related issues:
* https://github.com/LuaJIT/LuaJIT/issues/1403
* https://github.com/LuaJIT/LuaJIT/issues/1445
* https://github.com/tarantool/tarantool/issues/12134
Mike Pall (2):
Run VM events and finalizers in separate state.
Fix VM event error handling for finalizers.
src/lj_gc.c | 22 +++--
src/lj_obj.h | 2 +
src/lj_parse.c | 4 +-
src/lj_state.c | 1 +
src/lj_trace.c | 91 +++++++++----------
src/lj_vmevent.c | 5 +
src/lj_vmevent.h | 22 +++--
test/LuaJIT-tests/lang/gc_debug.lua | 11 +--
.../lj-1403-vmevent-crash-on-stkov.test.lua | 47 ++++++++++
.../lj-1445-errfin-errmsg.test.lua | 27 ++++++
10 files changed, 154 insertions(+), 78 deletions(-)
create mode 100644 test/tarantool-tests/lj-1403-vmevent-crash-on-stkov.test.lua
create mode 100644 test/tarantool-tests/lj-1445-errfin-errmsg.test.lua
--
2.53.0
next reply other threads:[~2026-03-28 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 15:31 Sergey Kaplun via Tarantool-patches [this message]
2026-03-28 15:31 ` [Tarantool-patches] [PATCH luajit 1/2] Run " Sergey Kaplun via Tarantool-patches
2026-03-28 15:31 ` [Tarantool-patches] [PATCH luajit 2/2] Fix VM event error handling for finalizers 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=cover.1774711616.git.skaplun@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/2] VM events and finalizers in separate state' \
/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