From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 1/3] merger: fix NULL dereference when called via iproto
Date: Fri, 19 Jun 2020 11:50:27 +0300 [thread overview]
Message-ID: <20200619085027.kcghsk32q4gad5zq@tkn_work_nb> (raw)
In-Reply-To: <811cb85f-f9e5-f353-68bb-010081d85eb2@tarantool.org>
> > static int
> > -luaL_merge_source_buffer_fetch(struct merge_source_buffer *source)
> > +luaL_merge_source_buffer_fetch_impl(struct lua_State *L,
> > + struct merge_source_buffer *source)
>
> I see my comment to the former first commit was missed somewhy, so I say
> it here:
Sorry, I misread it a bit and understood as part of illustration that
there are still no consistency even after dropping luaL prefix.
>
> - If a function takes lua_State, it is not mean it should get
> luaL_ prefix. Since the first commit was dropped, this comment
> we can't fix.
>
> - If a function is a method of struct, struct pointer goes *always*
> first, like 'this' argument in C++. Present of lua_State does
> not mean it should be first. This can and should be fixed, I think.
>
> This function in the first place is a method of merge_source_buffer.
> So it should take this argument first. luaL_merge_source_buffer_fetch_impl()
> currently is the only method of merge_source_buffer, which takes
> merge_source_buffer not in the first argument. It means, I don't see
> how the consistency is improved here. The same for
> luaL_merge_source_table_fetch, luaL_merge_source_table_next_impl,
> luaL_merge_source_tuple_fetch, luaL_merge_source_tuple_next_impl.
Moved <struct lua_State *> to the end of an argument list.
Removed the following paragraph from the commit message:
| Changed order of luaL_merge_source_tuple_fetch() arguments to unify it
| with other functions (<struct lua_State *>, <struct merge_source *>).
next prev parent reply other threads:[~2020-06-19 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 21:06 [Tarantool-patches] [PATCH v2 0/3] Merger's NULL defererence Alexander Turenko
2020-06-17 21:06 ` [Tarantool-patches] [PATCH v2 1/3] merger: fix NULL dereference when called via iproto Alexander Turenko
2020-06-18 22:48 ` Vladislav Shpilevoy
2020-06-19 8:50 ` Alexander Turenko [this message]
2020-06-19 23:32 ` Vladislav Shpilevoy
2020-06-21 18:28 ` Alexander Turenko
2020-07-01 20:36 ` Igor Munkin
2020-07-16 20:10 ` Alexander Turenko
2020-07-16 21:42 ` Igor Munkin
2020-07-16 22:44 ` Igor Munkin
2020-07-17 3:08 ` Alexander Turenko
2020-06-17 21:06 ` [Tarantool-patches] [PATCH v2 2/3] merger: clean fiber-local Lua stack after next() Alexander Turenko
2020-06-19 8:50 ` Alexander Turenko
2020-07-01 20:36 ` Igor Munkin
2020-07-16 20:11 ` Alexander Turenko
2020-07-16 22:07 ` Igor Munkin
2020-07-17 3:08 ` Alexander Turenko
2020-06-17 21:06 ` [Tarantool-patches] [PATCH v2 3/3] lua: expose temporary Lua state for iproto calls Alexander Turenko
2020-07-01 20:37 ` Igor Munkin
2020-07-16 20:11 ` Alexander Turenko
2020-07-16 22:33 ` Igor Munkin
2020-07-17 3:09 ` Alexander Turenko
2020-06-22 20:38 ` [Tarantool-patches] [PATCH v2 0/3] Merger's NULL defererence Vladislav Shpilevoy
2020-07-17 11:28 ` Alexander Turenko
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=20200619085027.kcghsk32q4gad5zq@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 1/3] merger: fix NULL dereference when called via iproto' \
/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