From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Maxim Kokryashkin <max.kokryashkin@gmail.com>, tarantool-patches@dev.tarantool.org, skaplun@tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit] Throw any errors before stack changes in trace stitching. Date: Tue, 20 Feb 2024 11:08:10 +0300 [thread overview] Message-ID: <0c07d575-620b-4832-bcc9-04a7ccbfa35e@tarantool.org> (raw) In-Reply-To: <20240216111152.152025-1-m.kokryashkin@tarantool.org> Hello, Max, thanks for the patch! see my comments Sergey On 2/16/24 14:11, Maxim Kokryashkin wrote: > From: Mike Pall <mike> > > Thanks to doujiang24. > > (cherry-picked from commit 3f9389edc6cdf3f78a6896d550c236860aed62b2) > > The Lua stack is changed in the `lj_record_stop`, so if the trace > is aborted, for example, when the `maxsnap` is reached, and an > error is thrown from there, the execution continues with an > unbalanced stack. > > Since the only error that is thrown from the `lj_record_stop` > with modified stack is `LJ_TRERR_SNAPOV`, this patch adds a As I see lj_record_stop [1] throws only LJ_TRERR_RETRY or I got you wrong. 1. https://github.com/LuaJIT/LuaJIT/blob/0d313b243194a0b8d2399d8b549ca5a0ff234db5/src/lj_record.c#L299 > check for snapshot overflow to the `recff_stitch`. > > Maxim Kokryashkin: > * added the description and the test for the problem > > Part of tarantool/tarantool#9595 > --- > Branch: https://github.com/tarantool/luajit/tree/fckxorg/lj-pr-720-errors-before-stitch > PR: https://github.com/tarantool/tarantool/pull/9703 > Issues: > https://github.com/tarantool/tarantool/issues/9595 > https://github.com/LuaJIT/LuaJIT/pull/720 > > src/lj_ffrecord.c | 4 ++++ > .../lj-pr-720-errors-before-stitch.test.lua | 20 +++++++++++++++++++ > 2 files changed, 24 insertions(+) > create mode 100644 test/tarantool-tests/lj-pr-720-errors-before-stitch.test.lua > > diff --git a/src/lj_ffrecord.c b/src/lj_ffrecord.c > index 1b2ddb72..e3ed80fb 100644 > --- a/src/lj_ffrecord.c > +++ b/src/lj_ffrecord.c > @@ -107,6 +107,10 @@ static void recff_stitch(jit_State *J) > const BCIns *pc = frame_pc(base-1); > TValue *pframe = frame_prevl(base-1); > > + /* Check for this now. Throwing in lj_record_stop messes up the stack. */ > + if (J->cur.nsnap >= (MSize)J->param[JIT_P_maxsnap]) > + lj_trace_err(J, LJ_TRERR_SNAPOV); > + > /* Move func + args up in Lua stack and insert continuation. */ > memmove(&base[1], &base[-1-LJ_FR2], sizeof(TValue)*nslot); > setframe_ftsz(nframe, ((char *)nframe - (char *)pframe) + FRAME_CONT); > diff --git a/test/tarantool-tests/lj-pr-720-errors-before-stitch.test.lua b/test/tarantool-tests/lj-pr-720-errors-before-stitch.test.lua > new file mode 100644 > index 00000000..53b7b5ea > --- /dev/null > +++ b/test/tarantool-tests/lj-pr-720-errors-before-stitch.test.lua You could omit "-pr" in the name, anyway https://github.com/LuaJIT/LuaJIT/issues/720 redirects to https://github.com/LuaJIT/LuaJIT/pull/720. > @@ -0,0 +1,20 @@ > +local tap = require('tap') > +local test = tap.test('lj-pr-720-errors-before-stitch'):skipcond({ > + ['Test requires JIT enabled'] = not jit.status(), > +}) > +test:plan(1) > + > +-- `math.modf` recording is NYI. > +local modf = require('math').modf > +jit.opt.start('hotloop=1', 'maxsnap=1') > + > +-- The loop has only two iterations: the first to detect its > +-- hotness and the second to record it. The snapshot limit is > +-- set to one and is certainly reached. > +for _ = 1, 2 do > + -- Forcify stitch. > + modf(1.2) > +end > + > +test:ok(true, 'stack is balanced') > +test:done(true) > -- > 2.43.0 >
next prev parent reply other threads:[~2024-02-20 8:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-16 11:11 Maxim Kokryashkin via Tarantool-patches 2024-02-20 8:08 ` Sergey Bronnikov via Tarantool-patches [this message] 2024-03-11 15:58 ` Sergey Bronnikov via Tarantool-patches 2024-02-21 12:34 ` Sergey Kaplun via Tarantool-patches 2024-02-22 14:03 ` 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=0c07d575-620b-4832-bcc9-04a7ccbfa35e@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=max.kokryashkin@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit] Throw any errors before stack changes in trace stitching.' \ /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