From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tarantool-patches@dev.tarantool.org,
Sergey Kaplun <skaplun@tarantool.org>
Subject: [Tarantool-patches] [PATCH luajit 0/3][v2] Fix stack overflow in pcall/xpcall
Date: Wed, 10 Dec 2025 10:23:25 +0300 [thread overview]
Message-ID: <cover.1765350224.git.sergeyb@tarantool.org> (raw)
The proposed patches fixes stack overflow in pcall/xpcall.
Related issues:
- https://github.com/LuaJIT/LuaJIT/issues/1048
- https://github.com/tarantool/tarantool/issues/11691
Git branch: https://github.com/tarantool/luajit/tree/ligurio/gh-xxxx-fix-stack-checks-in-vararg-calls
Changes in v2:
- Added patch for MIPS64
- Fixed issues reported on review
Mike Pall (3):
MIPS64: Fix xpcall() error case.
LJ_FR2: Fix stack checks in vararg calls.
Add stack check to pcall/xpcall.
src/lj_def.h | 2 +-
src/lj_dispatch.c | 2 +-
src/vm_arm.dasc | 7 ++
src/vm_arm64.dasc | 9 ++
src/vm_mips.dasc | 10 ++-
src/vm_mips64.dasc | 16 +++-
src/vm_ppc.dasc | 9 ++
src/vm_x64.dasc | 6 ++
src/vm_x86.dasc | 6 ++
...048-fix-stack-checks-vararg-calls.test.lua | 82 +++++++++++++++++++
10 files changed, 143 insertions(+), 6 deletions(-)
create mode 100644 test/tarantool-tests/lj-1048-fix-stack-checks-vararg-calls.test.lua
--
2.43.0
next reply other threads:[~2025-12-10 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 7:23 Sergey Bronnikov via Tarantool-patches [this message]
2025-12-10 7:23 ` [Tarantool-patches] [PATCH luajit 1/3] MIPS64: Fix xpcall() error case Sergey Bronnikov via Tarantool-patches
2025-12-10 7:23 ` [Tarantool-patches] [PATCH luajit 2/3][v2] LJ_FR2: Fix stack checks in vararg calls Sergey Bronnikov via Tarantool-patches
2025-12-10 7:23 ` [Tarantool-patches] [PATCH luajit 3/3][v2] Add stack check to pcall/xpcall Sergey Bronnikov 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.1765350224.git.sergeyb@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=estetus@gmail.com \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/3][v2] Fix stack overflow in pcall/xpcall' \
/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