Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: imeevma@tarantool.org
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1 1/2] sql: ignore \0 in string passed to C-function
Date: Wed, 31 Mar 2021 22:25:21 +0200	[thread overview]
Message-ID: <ced6bbd2-4714-0746-a3f4-9a76fbc0b9f4@tarantool.org> (raw)
In-Reply-To: <f4a4d7af1a22b15f88ef0ba8d8bae957c2338fe3.1617101707.git.imeevma@gmail.com>

Hi! Thanks for the patch!

See 4 comments below.

On 30.03.2021 13:21, Mergen Imeev via Tarantool-patches wrote:
> Prior to this patch string passed to user-defined C-function from SQL
> was cropped in case it contains '\0'. At the same time, it wasn't
> cropped if it is passed to the function from BOX. Now it isn't cropped
> when passed from SQL.
> 
> Part of #5938
> ---
> diff --git a/test/sql-tap/gh-5938-wrong-string-length.c b/test/sql-tap/gh-5938-wrong-string-length.c
> new file mode 100644
> index 000000000..96823f049
> --- /dev/null
> +++ b/test/sql-tap/gh-5938-wrong-string-length.c
> @@ -0,0 +1,42 @@
> +#include <msgpuck.h>

1. We use "" for non-system headers, not <>.

> +#include "module.h"
> +
> +enum
> +{

2. Enums have { on the same line as 'enum'.

> +	BUF_SIZE = 512,
> +};
> +
> +int
> +ret_str(box_function_ctx_t *ctx, const char *args, const char *args_end)
> +{
> +	uint32_t arg_count = mp_decode_array(&args);
> +	if (arg_count != 1) {
> +		return box_error_set(__FILE__, __LINE__, ER_PROC_C, "%s",
> +			"invalid argument count");

3. You don't need "%s", you can pass the error message right away.

4. The expression is misaligned. The same for the other box_error_set().

> +	}
> +	if (mp_typeof(*args) != MP_STR) {
> +		return box_error_set(__FILE__, __LINE__, ER_PROC_C, "%s",
> +			"argument should be string");
> +	}
> +	const char* str;
> +	uint32_t str_n;
> +	str = mp_decode_str(&args, &str_n);
> +
> +	uint32_t size = mp_sizeof_array(1) + mp_sizeof_str(str_n);
> +	if (size > BUF_SIZE) {
> +		return box_error_set(__FILE__, __LINE__, ER_PROC_C, "%s",
> +			"string is too long");
> +	}

  reply	other threads:[~2021-03-31 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 11:21 [Tarantool-patches] [PATCH v1 0/2] sql: ignore \0 in string passed to user function Mergen Imeev via Tarantool-patches
2021-03-30 11:21 ` [Tarantool-patches] [PATCH v1 1/2] sql: ignore \0 in string passed to C-function Mergen Imeev via Tarantool-patches
2021-03-31 20:25   ` Vladislav Shpilevoy via Tarantool-patches [this message]
2021-04-01  8:32     ` Mergen Imeev via Tarantool-patches
2021-03-30 11:21 ` [Tarantool-patches] [PATCH v1 2/2] sql: ignore \0 in string passed to Lua-function Mergen Imeev via Tarantool-patches
2021-03-31 20:25   ` Vladislav Shpilevoy via Tarantool-patches
2021-04-01  8:41     ` Mergen Imeev via Tarantool-patches
2021-04-01 12:01       ` Mergen Imeev via Tarantool-patches
2021-04-01 19:51       ` Vladislav Shpilevoy via Tarantool-patches
2021-04-01 22:50         ` Mergen Imeev via Tarantool-patches
2021-04-01 23:09 ` [Tarantool-patches] [PATCH v1 0/2] sql: ignore \0 in string passed to user function Vladislav Shpilevoy via Tarantool-patches
2021-04-02  7:55 ` Kirill Yukhin 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=ced6bbd2-4714-0746-a3f4-9a76fbc0b9f4@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imeevma@tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1 1/2] sql: ignore \0 in string passed to C-function' \
    /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