From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tarantool-patches@dev.tarantool.org,
Sergey Kaplun <skaplun@tarantool.org>,
Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Subject: [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table
Date: Tue, 9 Jul 2024 13:45:46 +0300 [thread overview]
Message-ID: <cover.1720521873.git.sergeyb@tarantool.org> (raw)
From: Sergey Bronnikov <sergeyb@tarantool.org>
Branch: https://github.com/tarantool/luajit/tree/ligurio/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer-nointegration
NOTE: Jobs with Tarantool regression tests has failed because
patch "FFI: Turn FFI finalizer table into a proper GC root."
broke Tarantool build and fix (see below) must be applied before
a bump to LuaJIT version with proposed patches.
Branch with fix in Tarantool: https://github.com/ligurio/tarantool/tree/ligurio/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer
Issues:
- https://github.com/luaJIT/luaJIT/issues/1168
- https://github.com/tarantool/tarantool/issues/10199
Mike Pall (2):
FFI: Treat cdata finalizer table as a GC root.
FFI: Turn FFI finalizer table into a proper GC root.
src/lib_ffi.c | 20 +---
src/lj_cdata.c | 2 +-
src/lj_ctype.c | 12 ++
src/lj_ctype.h | 2 +-
src/lj_gc.c | 38 +++---
src/lj_obj.h | 3 +
src/lj_state.c | 3 +
...free-on-access-to-CTState-finalizer.test.c | 108 ++++++++++++++++++
...ee-on-access-to-CTState-finalizer.test.lua | 18 +++
9 files changed, 165 insertions(+), 41 deletions(-)
create mode 100644 test/tarantool-c-tests/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer.test.c
create mode 100644 test/tarantool-tests/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer.test.lua
--
2.34.1
next reply other threads:[~2024-07-09 10:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 10:45 Sergey Bronnikov via Tarantool-patches [this message]
2024-07-09 10:45 ` [Tarantool-patches] [PATCH luajit 1/2][v2] FFI: Treat cdata finalizer table as a GC root Sergey Bronnikov via Tarantool-patches
2024-07-09 11:52 ` Sergey Kaplun via Tarantool-patches
2024-07-09 15:43 ` Sergey Bronnikov via Tarantool-patches
2024-07-10 13:13 ` Sergey Kaplun via Tarantool-patches
2024-07-23 18:18 ` Sergey Bronnikov via Tarantool-patches
2024-08-12 13:32 ` Sergey Kaplun via Tarantool-patches
2024-08-15 7:32 ` Sergey Bronnikov via Tarantool-patches
2024-08-15 8:33 ` Sergey Kaplun via Tarantool-patches
2024-07-09 10:45 ` [Tarantool-patches] [PATCH luajit 2/2][v2] FFI: Turn FFI finalizer table into a proper " Sergey Bronnikov via Tarantool-patches
2024-07-09 12:14 ` Sergey Kaplun via Tarantool-patches
2024-07-10 11:39 ` Sergey Bronnikov via Tarantool-patches
2024-07-10 14:08 ` Sergey Kaplun via Tarantool-patches
2024-07-23 18:29 ` Sergey Bronnikov via Tarantool-patches
2024-08-12 13:17 ` Sergey Kaplun via Tarantool-patches
2024-08-15 7:34 ` Sergey Bronnikov via Tarantool-patches
2024-08-15 8:34 ` Sergey Kaplun via Tarantool-patches
2024-07-09 11:54 ` [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table Sergey Kaplun via Tarantool-patches
2024-07-10 11:41 ` Sergey Bronnikov via Tarantool-patches
2024-08-15 8:15 Sergey Bronnikov via Tarantool-patches
2024-08-15 12:16 ` 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.1720521873.git.sergeyb@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=estetus@gmail.com \
--cc=m.kokryashkin@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table' \
/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