From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: Sergey Bronnikov <estetus@gmail.com>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 1/2][v2] FFI: Treat cdata finalizer table as a GC root. Date: Mon, 12 Aug 2024 16:32:28 +0300 [thread overview] Message-ID: <ZroO7BXtZTer6kka@root> (raw) In-Reply-To: <d07c195f-2ada-4eb5-85b2-a24631f73d8e@tarantool.org> Hi, Sergey! Thanks for the fixes! On 23.07.24, Sergey Bronnikov wrote: > Hi, > > please see comments below. Fixes applied and force-pushed. > > Sergey > > On 10.07.2024 16:13, Sergey Kaplun wrote: > > Hi, Sergey! > > Thanks for the fixes! > > Please consider my minor nits about comments below. > > > > On 09.07.24, Sergey Bronnikov wrote: > >> Hi, Sergey, > >> > >> thanks for review. Fixes applied and force-pushed. > >> > >> Sergey > >> > >> > >> On 09.07.2024 14:52, Sergey Kaplun via Tarantool-patches wrote: > >>> Hi, Sergey! > >>> Thanks for the patch! > >>> Please consider my comments below. > >>> > >>> On 09.07.24, Sergey Bronnikov wrote: > >>>> From: Mike Pall <mike> > >>>> <snipped> > > > > It is more correct to say, that "`lua_State` is marked after the > > function is removed from it" (since we stop the GC before chunk > > loading and starts after). My bad: Typo: s/starts/start/ > > <snipped> > >>> Also, it is worth mentioning that the problem was partially solved, the > >>> complete fix will be applied in the next patch. > Added. > > Please, add its description to the commit message too. I would rephrase this part as the following: | The patch fixes the problem partially by marking the finalizer table | on the start of the GC cycle. | The complete fix will be applied in the next patch by turning the | finalizer table into the proper GC root. > > > >>>> Sergey Bronnikov: > >>>> * added the description and the tests for the problem > >>>> > >>>> Part of tarantool/tarantool#10199 > >>>> --- > >>>> src/lj_gc.c | 3 + > >>>> ...free-on-access-to-CTState-finalizer.test.c | 66 +++++++++++++++++++ > >>>> ...ee-on-access-to-CTState-finalizer.test.lua | 18 +++++ > >>>> 3 files changed, 87 insertions(+) > >>>> 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 > > <snipped> > > > >> > >>>> + * has the finalizer table as its environment. But, there is no > >>>> + * FFI module table anywhere to anchor the `ffi.gc` itself, and > >>>> + * the `lua_State` object was marked before the function is > > It is more correct to say, that "`lua_State` is marked after the > > function is removed from it" (since we stop the GC before chunk > > loading and starts after). My bad: Typo: s/starts/start/ > > <snipped> > >>>> + if (luaL_loadbufferx(L, buff, sizeof(buff) - 1, "chunk", "t") != LUA_OK) > >>> Why do we need to omit the ending zero byte? Please add a comment that the terminating '\0' is considered by parser as part of the input, so we must chomp it. > > > > <snipped> > > > >>>> diff --git a/test/tarantool-tests/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer.test.lua b/test/tarantool-tests/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer.test.lua > >>>> new file mode 100644 > >>>> index 00000000..fca5ec76 > >>>> --- /dev/null > >>>> +++ b/test/tarantool-tests/lj-1168-heap-use-after-free-on-access-to-CTState-finalizer.test.lua <snipped> > >>>> 2.34.1 > >>>> -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2024-08-12 13:32 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-09 10:45 [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table Sergey Bronnikov via Tarantool-patches 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 [this message] 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 8:20 ` [Tarantool-patches] [PATCH luajit 1/2][v2] FFI: Treat cdata finalizer table as a GC root Sergey Bronnikov via Tarantool-patches 2024-08-15 8:59 ` Maxim Kokryashkin 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=ZroO7BXtZTer6kka@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 1/2][v2] FFI: Treat cdata finalizer table as a GC root.' \ /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