1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify plugin_ref lifetimes in function comments

Browse Source 
The mechanism in plugin_lock() et.al. which automatically unlocks
plugins unless called with NULL THD is quite subtle, and deserves
proper documentation.

(This was found during MDEV-12179 development, but is independent of
it, and so done in a separate commit).
This commit is contained in:
Kristian Nielsen 2017-04-20 16:11:14 +02:00
parent da9decdccf
commit 094e4b264c
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
sql/sql_plugin.cc
View File

@ -938,6 +938,10 @@ SHOW_COMP_OPTION plugin_status(const char *name, size_t len, int type)
}
/*
If LEX is passed non-NULL, an automatic unlock of the plugin will happen
in the LEX destructor.
*/
static plugin_ref intern_plugin_lock(LEX *lex, plugin_ref rc)
{
st_plugin_int *pi= plugin_ref_to_int(rc);
@ -981,6 +985,16 @@ static plugin_ref intern_plugin_lock(LEX *lex, plugin_ref rc)
}
/*
Notes on lifetime:
If THD is passed as non-NULL (and with a non-NULL thd->lex), an entry is made
in the thd->lex which will cause an automatic unlock of the plugin in the LEX
destructor. In this case, no manual unlock must be done.
Otherwise, when passing a NULL THD, the caller must arrange that plugin
unlock happens later.
*/
plugin_ref plugin_lock(THD *thd, plugin_ref ptr)
{
LEX *lex= thd ? thd->lex : 0;
@ -1017,6 +1031,16 @@ plugin_ref plugin_lock(THD *thd, plugin_ref ptr)
}
/*
Notes on lifetime:
If THD is passed as non-NULL (and with a non-NULL thd->lex), an entry is made
in the thd->lex which will cause an automatic unlock of the plugin in the LEX
destructor. In this case, no manual unlock must be done.
Otherwise, when passing a NULL THD, the caller must arrange that plugin
unlock happens later.
*/
plugin_ref plugin_lock_by_name(THD *thd, const LEX_STRING *name, int type)
{
LEX *lex= thd ? thd->lex : 0;