From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit] Fix limit check in narrow_conv_backprop(). Date: Tue, 17 Sep 2024 15:01:17 +0300 [thread overview] Message-ID: <Zulvjeoswb9O-8Ov@root> (raw) In-Reply-To: <8178af4b-fa35-44c2-b3fd-6e563eb660d5@tarantool.org> Hi, Sergey! Thanks for the review! On 17.09.24, Sergey Bronnikov wrote: > Hi, Sergey, > > thanks for tha patch! LGTM with a minor comment below. > > On 26.08.2024 15:37, Sergey Kaplun wrote: > > From: Mike Pall <mike> <snipped> > > +-- XXX: Test fails only under ASAN. > > +-- XXX: The original reproducer was found by fuzzer: > > +--https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70779. > > +-- It creates a long side trace with a huge amount of ADD IRs, > > +-- which are recursively used in the `narrow_conv_backprop()` many > > +-- enough times to catch the stack-buffer-overflow. I can't > > +-- simplify the reproducer any more (or write it from scratch), so > > +-- I leave it in that state. > > + > > I would remove a sentence "I can't simplify the reproducer ..." > > from the test, because it is useful information on review and > > I think it is useless for those who will use the test. I do not agree -- it is kind of worning to prevent changing the test. Also, we have something similar for gh-4199-gc64-fuse, for example. > > Feel free to ignore and leave as is. So, ignoring for now. > > > s/any more/anymore/ I decided to drop any, so the comment is the following now: =================================================================== diff --git a/test/tarantool-tests/lj-1262-fix-limit-narrow-conv-backprop.test.lua b/test/tarantool-tests/lj-1262-fix-limit-narrow-conv-backprop.test.lua index 6bb4025d..c225fa14 100644 --- a/test/tarantool-tests/lj-1262-fix-limit-narrow-conv-backprop.test.lua +++ b/test/tarantool-tests/lj-1262-fix-limit-narrow-conv-backprop.test.lua @@ -15,9 +15,9 @@ test:plan(1) -- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70779. -- It creates a long side trace with a huge amount of ADD IRs, -- which are recursively used in the `narrow_conv_backprop()` many --- enough times to catch the stack-buffer-overflow. I can't --- simplify the reproducer any more (or write it from scratch), so --- I leave it in that state. +-- enough times to catch the stack-buffer-overflow. I can't more +-- simplify the reproducer any (or write it from scratch), so I +-- leave it in that state. local DEFAULT_NUMBER = 1 local tonumber = tonumber =================================================================== <snipped> -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2024-09-17 12:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-26 12:37 Sergey Kaplun via Tarantool-patches 2024-09-17 10:32 ` Sergey Bronnikov via Tarantool-patches 2024-09-17 12:01 ` Sergey Kaplun via Tarantool-patches [this message] 2024-09-23 6:41 ` Maxim Kokryashkin via Tarantool-patches 2024-09-23 6:57 ` Sergey Kaplun via Tarantool-patches 2024-10-18 15:15 ` Sergey Kaplun 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=Zulvjeoswb9O-8Ov@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit] Fix limit check in narrow_conv_backprop().' \ /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