Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin <imun@tarantool.org>
To: Sergey Ostanevich <sergos@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] serializer: check for recursive serialization
Date: Tue, 8 Dec 2020 20:25:22 +0300	[thread overview]
Message-ID: <20201208172522.GL5396@tarantool.org> (raw)
In-Reply-To: <B047972B-C8D5-4262-A49B-F79CC3D12578@tarantool.org>

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?

> 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

  reply	other threads:[~2020-12-08 17:25 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 [this message]
2020-12-11  3:22         ` Roman Khabibov

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=20201208172522.GL5396@tarantool.org \
    --to=imun@tarantool.org \
    --cc=sergos@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