From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Handle stack reallocation in debug.setmetatable() and lua_setmetatable().
Date: Tue, 12 Mar 2024 08:43:44 +0300 [thread overview]
Message-ID: <Ze_rkIe3b4IN8lRa@root> (raw)
In-Reply-To: <pjr6gl3xxhy4mtmwxcn3okorvtm6vd352widh63p2qe62wltct@qk2uz6z3qbr6>
Hi, Maxim!
Thanks for the review!
Please consider my answers below.
On 11.03.24, Maxim Kokryashkin wrote:
> Hi, Sergey!
> Thanks for the patch!
> Please consider my comments below.
>
> The test passes before the patch, as can be seen in CI for this branch:
> https://github.com/tarantool/luajit/tree/mkokryashkin/test
I see quite the opposite [1][2].
>
> On Mon, Mar 11, 2024 at 01:37:01PM +0300, Sergey Kaplun wrote:
<snipped>
> > ---
> >
> > Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-1172-debug-handling-ref
> > Tarantool PR: https://github.com/tarantool/tarantool/pull/9786
> > Related issues:
> > * https://github.com/tarantool/tarantool/issues/9595
> > * https://github.com/LuaJIT/LuaJIT/issues/1172
> >
> >
> > src/lj_api.c | 1 +
> > .../lj-1172-debug-handling-ref.test.lua | 30 +++++++++++++++++++
> > 2 files changed, 31 insertions(+)
> > create mode 100644 test/tarantool-tests/lj-1172-debug-handling-ref.test.lua
> >
> > diff --git a/src/lj_api.c b/src/lj_api.c
> > index 3bacad33..2e915306 100644
> > --- a/src/lj_api.c
> > +++ b/src/lj_api.c
<snipped>
> > diff --git a/test/tarantool-tests/lj-1172-debug-handling-ref.test.lua b/test/tarantool-tests/lj-1172-debug-handling-ref.test.lua
> > new file mode 100644
> > index 00000000..cac1c223
<snipped>
> > +local jdump = require('jit.dump')
> > +
> > +test:plan(1)
> > +
> > +jdump.start('t', '/dev/null')
> Why do we need that call here?
Because we need to trigger the VM event, see the comment below.
> > +
> > +-- Use `coroutine.wrap()` to create a new Lua stack with a minimum
> > +-- number of stack slots.
> > +coroutine.wrap(function()
> > + -- "TRACE flush" event handler causes stack reallocation and
> How is flush event caused?
By the `jit.dump()` as most VM events.
> > + -- leads to heap-use-after-free. This event handler is called
> > + -- because all traces are specialized to base metatables, so
> > + -- if we update any base metatable, we must flush all traces.
> > + debug.setmetatable(1, {})
> > +end)()
> > +
> > +test:ok(true, 'no heap-use-after-free error')
> > +
> > +test:done(true)
> > --
> > 2.44.0
> >
[1]: https://github.com/tarantool/luajit/actions/runs/8239484621/job/22532793546#step:6:1344
[2]: https://github.com/tarantool/luajit/actions/runs/8239484621/job/22532793913#step:6:1363
--
Best regards,
Sergey Kaplun
next prev parent reply other threads:[~2024-03-12 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 10:37 Sergey Kaplun via Tarantool-patches
2024-03-11 20:50 ` Maxim Kokryashkin via Tarantool-patches
2024-03-12 5:43 ` Sergey Kaplun via Tarantool-patches [this message]
2024-03-12 11:58 ` Maxim Kokryashkin via Tarantool-patches
2024-03-13 7:46 ` Sergey Kaplun via Tarantool-patches
2024-03-13 8:49 ` Maxim Kokryashkin via Tarantool-patches
2024-04-04 9:38 ` Sergey Bronnikov via Tarantool-patches
2024-04-11 17:02 ` 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=Ze_rkIe3b4IN8lRa@root \
--to=tarantool-patches@dev.tarantool.org \
--cc=m.kokryashkin@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit] Handle stack reallocation in debug.setmetatable() and lua_setmetatable().' \
/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