From: Cyrill Gorcunov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tml <tarantool-patches@dev.tarantool.org> Cc: Mons Anderson <v.perepelitsa@corp.mail.ru>, Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Subject: [Tarantool-patches] [PATCH v15 05/11] module_cache: add comment about weird resolving Date: Fri, 5 Feb 2021 21:54:30 +0300 [thread overview] Message-ID: <20210205185436.638894-6-gorcunov@gmail.com> (raw) In-Reply-To: <20210205185436.638894-1-gorcunov@gmail.com> The module management is not obvious when reading the code, mostly because of weird design in first place which we can't change without breaking backward compatibility. Add a note about this into code itself otherwise it is hard to understand why it works the way it does. Part-of #4642 Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- src/box/module_cache.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/box/module_cache.c b/src/box/module_cache.c index e8a510d26..f606ec327 100644 --- a/src/box/module_cache.c +++ b/src/box/module_cache.c @@ -418,6 +418,18 @@ int module_sym_call(struct module_sym *mod_sym, struct port *args, struct port *ret) { + /* + * The functions created with `box.schema.func` + * help are not resolved immediately. Instead + * they are deferred until first call. And when + * call happens the we try to load a module and + * resolve a symbol (which of course can fail if + * there is no such module at all). + * + * While this is very weird (and frankly speaking + * very bad design) we can't change it for backward + * compatibility sake! + */ if (mod_sym->addr == NULL) { if (module_sym_load(mod_sym) != 0) return -1; -- 2.29.2
next prev parent reply other threads:[~2021-02-05 18:57 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-05 18:54 [Tarantool-patches] [PATCH v15 00/11] box: implement cmod Lua module Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 01/11] box/func: factor out c function entry structure Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 02/11] module_cache: move module handling into own subsystem Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 03/11] module_cache: direct update a cache value on reload Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 04/11] module_cache: rename calls to ref in module structure Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` Cyrill Gorcunov via Tarantool-patches [this message] 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 06/11] module_cache: module_reload - drop redundant parameter Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 07/11] module_cache: use references as a main usage counter Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-08 11:54 ` Cyrill Gorcunov via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 08/11] module_cache: make module to carry hash it belongs to Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 09/11] module_cache: use own hash for box.schema.func requests Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 10/11] box/cmod: implement cmod Lua module Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-05 18:54 ` [Tarantool-patches] [PATCH v15 11/11] test: box/cfunc -- add cmod test Cyrill Gorcunov via Tarantool-patches 2021-02-07 17:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-07 17:21 ` Vladislav Shpilevoy via Tarantool-patches 2021-02-06 17:55 ` [Tarantool-patches] [PATCH v15 00/11] box: implement cmod Lua module Vladislav Shpilevoy 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=20210205185436.638894-6-gorcunov@gmail.com \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=v.perepelitsa@corp.mail.ru \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v15 05/11] module_cache: add comment about weird resolving' \ /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