From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: imeevma@tarantool.org
Subject: [tarantool-patches] Re: [PATCH v7 1/6] lua: remove exceptions from function luaL_tofield()
Date: Thu, 17 Jan 2019 14:41:07 +0300 [thread overview]
Message-ID: <20190117114107.GL28204@chai> (raw)
In-Reply-To: <09d7de8e-0565-50aa-8243-5bb7ca4ee623@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/01/16 21:29]:
I don't mind if we have a cpcall even in scope of this patch - but
let's test these errors, not just rewrite the code and hope for
the best.
Can we have any kind of test which runs in short time for lua
errors?
> 3. In my opinion there is still a problem with lua_* methods,
> throwing exceptions on OOM *and on a simple stack overflow*.
> Even fixed GC will not fix the problem if all memory is
> occupied by non-garbage memory. I adhere to my opinion that it
> is better to use lua_cpcall. There is nothing bad with it. *_pcall
> just remembers a couple of registers, it is not too expensive for
> such a vast function. Also lua_cpcall causes much less diff.
>
> We can do it, for example, by renaming luaL_tofield to luaL_tofield_xc
> and introducing new luaL_tofield, calling luaL_tofield_xc via
> lua_cpcall. Just like we used to work with C++ *_xc wrappers.
>
> Please, ask again in the server team chat about the proposal above.
> Do not forget about stack overflow error, which also is possible and
> does not mean panic. Moreover, it is worth noting that diff is going
> to be much less and simpler. If they decline the proposal, I give in.
>
> > - luaL_tofield(L, cfg, idx, field);
> > - return;
> > + return luaL_tofield(L, cfg, idx, field);
> > } else if (!lua_isstring(L, -1)) {
> > - luaL_error(L, "invalid " LUAL_SERIALIZE " value");
> > + diag_set(ClientError, ER_PROC_LUA,
> > + "invalid " LUAL_SERIALIZE " value");
> > + return -1;
> > }
> > type = lua_tostring(L, -1);
> > @@ -525,94 +539,96 @@ luaL_tofield(struct lua_State *L, struct luaL_serializer *cfg, int index,
> > field->dval = num;
> > CHECK_NUMBER(num);
> > }
> > - return;
> > + break;
>
> 4. Why no to return 0? Anyway all your breaks lead to a simple 'return 0'.
>
> > @@ -620,14 +636,15 @@ luaL_tofield(struct lua_State *L, struct luaL_serializer *cfg, int index,
> > field->sval.len = 0;
> > if (lua_touserdata(L, index) == NULL) {
> > field->type = MP_NIL;
> > - return;
> > + break;
> > }
> > /* Fall through */
> > default:
> > field->type = MP_EXT;
> > - return;
> > + break;
> > }
> > #undef CHECK_NUMBER
> > + return 0;
> > }
> > void
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2019-01-17 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 16:10 [tarantool-patches] [PATCH v7 0/6] sql: remove box.sql.execute imeevma
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 1/6] lua: remove exceptions from function luaL_tofield() imeevma
2019-01-16 18:25 ` [tarantool-patches] " Vladislav Shpilevoy
2019-01-17 11:40 ` Konstantin Osipov
2019-01-17 11:41 ` Konstantin Osipov [this message]
2019-01-17 11:38 ` Konstantin Osipov
2019-01-17 13:15 ` Vladislav Shpilevoy
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 2/6] iproto: move map creation to sql_response_dump() imeevma
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 3/6] iproto: create port_sql imeevma
2019-01-16 18:25 ` [tarantool-patches] " Vladislav Shpilevoy
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 4/6] lua: create method dump_lua for port_sql imeevma
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 5/6] lua: parameter binding for new execute() imeevma
2019-01-15 16:10 ` [tarantool-patches] [PATCH v7 6/6] sql: check new box.sql.execute() imeevma
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=20190117114107.GL28204@chai \
--to=kostja@tarantool.org \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v7 1/6] lua: remove exceptions from function luaL_tofield()' \
/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