From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit v1 5/5] Use generic trace error for OOM during trace stitching. Date: Thu, 13 Jun 2024 13:31:26 +0300 [thread overview] Message-ID: <ZmrKfnnRy9rBYiN3@root> (raw) In-Reply-To: <ae9054d5-2644-46f1-84fb-4a652f21ab27@tarantool.org> Hi, Sergey! Thanks for the review! Please consider my answers below. On 06.06.24, Sergey Bronnikov wrote: > Sergey, > > > thanks for the patch! See my comments below. > > > Sergey > > On 22.04.2024 11:49, Sergey Kaplun wrote: > > From: Mike Pall <mike> > > > > Thanks to Sergey Kaplun. > > > > (cherry picked from commit b8b49bf3954b23e32e34187a6ada00021c26e172) > > > > The previous commit doesn't handle the case when the error code is > > `LUA_ERRMEM`. This patch adds a workaround by using the generic error > > message. > > > > Sergey Kaplun: > > * added the description and the test for the problem > > > > Part of tarantool/tarantool#9924 > > --- > > src/lj_ffrecord.c | 2 + > > .../lj-1166-error-stitch-oom-ir-buff.test.lua | 41 ++++++++++++++++++- > > ...j-1166-error-stitch-oom-snap-buff.test.lua | 37 +++++++++++++++-- > > 3 files changed, 75 insertions(+), 5 deletions(-) > > > > diff --git a/src/lj_ffrecord.c b/src/lj_ffrecord.c > > index ff14e9e4..d5fc081e 100644 > > --- a/src/lj_ffrecord.c > > +++ b/src/lj_ffrecord.c > > @@ -150,6 +150,8 @@ static void recff_stitch(jit_State *J) > > if (errcode) { > > if (errcode == LUA_ERRRUN) > > copyTV(L, L->top-1, L->top + (1 + LJ_FR2)); > > + else > > + setintV(L->top-1, (int32_t)LJ_TRERR_RECERR); > > lj_err_throw(L, errcode); /* Propagate errors. */ > > } > > } > > diff --git a/test/tarantool-tests/lj-1166-error-stitch-oom-ir-buff.test.lua b/test/tarantool-tests/lj-1166-error-stitch-oom-ir-buff.test.lua > > index e3a5397d..cf3ab0f5 100644 > > --- a/test/tarantool-tests/lj-1166-error-stitch-oom-ir-buff.test.lua > > +++ b/test/tarantool-tests/lj-1166-error-stitch-oom-ir-buff.test.lua <snipped> > > +test:skipcond({ > > + -- luacheck: no global > > I made a patch that remove inline suppressions [1]. > > I propose to merge it and remove inline suppressions in your patch > series too. Ok, I'll remove these supressions after merging your patch and rebasing to the master. <snipped> > > > > +-- We only need the abort reason in the test. > > +jparse.start('t') > Same comment as in previous mail - let's add a comment regarding 't'. See my answers here [1]. > > + > > -- XXX: Update hotcounts to avoid hash collisions. > > jit.opt.start('hotloop=1') > > - > > jit.on() > > > > mockalloc.mock() > > @@ -49,6 +58,28 @@ tracef() > > > > mockalloc.unmock() > Same comment as in previous mail - let's avoid name 'mock' here. But we actually mock the allocator here, don't we? Thus, I renamed the new allocated function to avoid confusion. If you insist, please suggest the correct name instead `mock` | `unmock`. > > <snipped> > > test:done(true) [1]: https://lists.tarantool.org/pipermail/tarantool-patches/2024-June/029218.html -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2024-06-13 10:35 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 8:49 [Tarantool-patches] [PATCH luajit v1 0/5] Handle all errors during stitching Sergey Kaplun via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 1/5] build: introduce option LUAJIT_ENABLE_TABLE_BUMP Sergey Kaplun via Tarantool-patches 2024-05-05 12:39 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:47 ` Sergey Kaplun via Tarantool-patches 2024-06-06 10:53 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 9:51 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:37 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 2/5] ci: add tablebump flavor for exotic builds Sergey Kaplun via Tarantool-patches 2024-05-05 12:40 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:49 ` Sergey Kaplun via Tarantool-patches 2024-06-06 10:56 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 3/5] test: allow `jit.parse` to return aborted traces Sergey Kaplun via Tarantool-patches 2024-05-05 12:55 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:53 ` Sergey Kaplun via Tarantool-patches 2024-06-06 11:01 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:00 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:38 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 4/5] Handle all types of errors during trace stitching Sergey Kaplun via Tarantool-patches 2024-05-06 8:25 ` Maxim Kokryashkin via Tarantool-patches 2024-06-06 13:03 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:25 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:52 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 5/5] Use generic trace error for OOM " Sergey Kaplun via Tarantool-patches 2024-05-06 8:27 ` Maxim Kokryashkin via Tarantool-patches 2024-06-06 14:06 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:31 ` Sergey Kaplun via Tarantool-patches [this message] 2024-06-13 14:58 ` Sergey Bronnikov via Tarantool-patches 2024-06-16 19:13 ` 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=ZmrKfnnRy9rBYiN3@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v1 5/5] Use generic trace error for OOM during 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