From: Roman Khabibov <roman.habibov@tarantool.org>
To: Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] serializer: check for recursive serialization
Date: Fri, 11 Dec 2020 08:22:23 +0500 [thread overview]
Message-ID: <2230BA89-2905-4A22-A74A-BB59FC53136B@tarantool.org> (raw)
In-Reply-To: <20201208172522.GL5396@tarantool.org>
Hi!
> On Dec 8, 2020, at 22:25, Igor Munkin <imun@tarantool.org> wrote:
>
> Sergos,
>
> On 08.12.20, Sergey Ostanevich wrote:
>> Hi!
>>
>> Thanks for the patch!
>>
>> My biggest concern was how would you check the recursion appears. You
>
> Well, I see the issue is reported for "identity" serializer (considering
> documentation request and the error message), and such recursion can be
> fixed the way Roma did. You're talking about a general case of infinite
> recursions, but I believe there is no other approach to handle this
> situation the way different from one Python does (I mentioned it in my
> previous review[1]). By the way, other runtimes such as Perl starts
> spamming with the corresponding warning after the recursion hits the
> "soft" limit, but the result is the same: stack overflow. Thoughts?
Let’s just add ‘hard’ limit? Only it is not clear how to calculate its
value. Just empirically?
>> just check if the result is equivalent to the argument. To me it is
>> not enough, obviously. I tried this on your branch and…
>>
>>
>> tarantool> setmetatable({},{__serialize = function(_) return {_} end})
>> Segmentation fault (core dumped)
>>
>>
>> Regards,
>> Sergos
>>
>
> <snipped>
>
>>
>
> [1]: https://lists.tarantool.org/pipermail/tarantool-patches/2020-July/018524.html
>
> --
> Best regards,
> IM
prev parent reply other threads:[~2020-12-11 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 16:40 Roman Khabibov
2020-11-23 20:28 ` Igor Munkin
2020-11-24 1:51 ` roman
2020-12-02 0:53 ` Roman Khabibov
2020-12-08 16:59 ` Sergey Ostanevich
2020-12-08 17:25 ` Igor Munkin
2020-12-11 3:22 ` Roman Khabibov [this message]
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=2230BA89-2905-4A22-A74A-BB59FC53136B@tarantool.org \
--to=roman.habibov@tarantool.org \
--cc=imun@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] serializer: check for recursive serialization' \
/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