From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp61.i.mail.ru (smtp61.i.mail.ru [217.69.128.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 8DB48445320 for ; Tue, 14 Jul 2020 14:03:22 +0300 (MSK) Date: Tue, 14 Jul 2020 14:03:21 +0300 From: Kirill Yukhin Message-ID: <20200714110321.5w3m67lb62hlrrdb@tarantool.org> References: <20200703133255.23820-1-i.kosarev@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200703133255.23820-1-i.kosarev@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] engine: validate key in space_before_replace List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ilya Kosarev Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org Hello, On 03 июл 16:32, Ilya Kosarev wrote: > Since 9fba29abb4e05babb9b23b4413bd8083f0fba933 (memtx: introduce tuple > compare hint) index_get uses key_hint to get a comparison hint for the > key. It requires key type to be validated. However in > space_before_replace index_get was used without key validation on some > execution paths. Now it is fixed and validation is being performed if > needed. Corresponding test case is introduced. > > Closes #5093 > --- > Branch: https://github.com/tarantool/tarantool/tree/i.kosarev/gh-5093-before_replace-key-validation > Issue: https://github.com/tarantool/tarantool/issues/5093 LGTM. I've checked your patch into 2.3, 2.4 and master. -- Regards, Kirill Yukhin