From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Aleksandr Lyapunov <alyapunov@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 02/15] Check data_offset overflow in struct tuple Date: Sun, 5 Jul 2020 19:03:47 +0200 [thread overview] Message-ID: <0ce23cdd-5a37-e1a3-3b3c-c949120c9e96@tarantool.org> (raw) In-Reply-To: <1593757997-4145-3-git-send-email-alyapunov@tarantool.org> Thanks for the patch! See 3 comments below. > diff --git a/test/box/huge_field_map.result b/test/box/huge_field_map.result > new file mode 100644 > index 0000000..11b4da3 > --- /dev/null > +++ b/test/box/huge_field_map.result > @@ -0,0 +1,49 @@ > +-- test-run result file version 2 > +env = require('test_run') > + | --- > + | ... > +test_run = env.new() > + | --- > + | ... > + > +s = box.schema.space.create('test', {engine = 'memtx'}) > + | --- > + | ... > +i1 = s:create_index('pk') > + | --- > + | ... > +i2 = s:create_index('mk', {parts={{'[2][*]', 'uint'}}}) 1. Why do you need a multikey index? This test lacks a comment. > + | --- > + | ... > +test_run:cmd("setopt delimiter ';'") > + | --- > + | - true > + | ... > diff --git a/test/box/huge_field_map_long.result b/test/box/huge_field_map_long.result > new file mode 100644 > index 0000000..d7971ae > --- /dev/null > +++ b/test/box/huge_field_map_long.result > @@ -0,0 +1,51 @@ > +-- test-run result file version 2 > +env = require('test_run') > + | --- > + | ... > +test_run = env.new() > + | --- > + | ... > + > +s = box.schema.space.create('test', {engine = 'memtx'}) 2. I saw you also fixed vinyl and runtime tuples. I suppose you need to test them as well. > + | --- > + | ... > +test_run:cmd("setopt delimiter ';'") > + | --- > + | - true > + | ... > +function test() > + local t = {} > + local k = {} > + for i = 1,128 do > + local parts = {} > + for j = 0,127 do > + table.insert(parts, {i * 128 - j, 'uint'}) > + table.insert(t, 1) > + end > + if i == 1 then k = table.deepcopy(t) end > + s:create_index('test'..i, {parts = parts}) > + if i % 16 == 0 then > + s:replace(t) > + s:delete(k) > + end > + end > +end; > + | --- > + | ... > +test_run:cmd("setopt delimiter ''"); > + | --- > + | - true > + | ... > + > +pcall(test) -- must fail but not crash > + | --- > + | - false > + | - 'Can''t create tuple: metadata size 65542 is too big' > + | ... > + > +test = nil > + | --- > + | ... > +s:drop() > + | --- > + | ... > diff --git a/test/box/huge_field_map_long.test.lua b/test/box/huge_field_map_long.test.lua > new file mode 100644 3. Why do you need a 'long' test? The first test seems to be good enough.
next prev parent reply other threads:[~2020-07-05 17:03 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-03 6:33 [Tarantool-patches] [PATCH 00/15] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 01/15] Update license file (2020) Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 02/15] Check data_offset overflow in struct tuple Aleksandr Lyapunov 2020-07-05 17:03 ` Vladislav Shpilevoy [this message] 2020-07-06 13:39 ` Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 03/15] tx: introduce dirty tuples Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 04/15] vinyl: rename tx_manager -> vy_tx_manager Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 05/15] tx: save txn in txn_stmt Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 06/15] tx: add TX status Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 07/15] tx: save preserve old tuple flag in txn_stmt Aleksandr Lyapunov 2020-07-05 17:05 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 08/15] tx: introduce tx manager Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 09/15] tx: introduce prepare sequence number Aleksandr Lyapunov 2020-07-05 17:05 ` Vladislav Shpilevoy 2020-07-06 13:50 ` Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 10/15] tx: introduce txn_stmt_destroy Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 11/15] tx: introduce conflict tracker Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 12/15] tx: introduce txm_story Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 13/15] tx: indexes Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 14/15] tx: introduce point conflict tracker Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 15/15] tx: use new tx managet in memtx Aleksandr Lyapunov 2020-07-05 17:03 ` [Tarantool-patches] [PATCH 00/15] Transaction engine for memtx engine Vladislav Shpilevoy 2020-07-06 13:29 ` Aleksandr Lyapunov
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=0ce23cdd-5a37-e1a3-3b3c-c949120c9e96@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 02/15] Check data_offset overflow in struct tuple' \ /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