Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: Sergey Bronnikov <estetus@gmail.com>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit v2 1/1] Fix saved bytecode encapsulated in ELF objects.
Date: Tue, 6 Jun 2023 15:55:26 +0300	[thread overview]
Message-ID: <ZH8svivoxaDyDHiF@root> (raw)
In-Reply-To: <8e60e454-de80-e532-ee1d-ad771956ab16@tarantool.org>

Hi, Maxim, Sergey!
Thanks for the comments!

On 31.05.23, Sergey Bronnikov wrote:
> Hello, Max! Thanks for comments!
> 
> Fixed all comments except checks for constant size and offset, fixes 
> force-pushed.
> 
> 
> Sergey
> 
> On 5/30/23 12:05, Maxim Kokryashkin wrote:
> > Hi, Sergey!
> > Thanks for the patch!
> > LGTM, except for a few comments below.

<snipped>

> >         +
> >         +test:is(strtab_size, expected_strtab_size, 'check .strtab size')
> >         +test:is(strtab_offset, expected_strtab_offset, 'check .strtab
> >         offset')
> >
> >     As I already said offline, I don’t like that approach. ELF is made
> >     to by
> >     as flexible as possible, so, generally, you have no guarantees about
> >     order and, hence, offsets of any sections. The only reason why we are
> >     getting away with that here, is because this ELF is generated
> >     in `bcsave.lua` in a particular manner. It is ok for now, but no one
> >     knows if this will ever change. I think that the symbol name search
> >     below is sufficient, because it is unlikely to pass with an
> >     incorrect offset.

But, the finding the symbol, doesn't guarantee the correct offset
emitting. I suggest to leave double check here, too, as well as Sergey.
Also, we can track the changes in <jit/bcsave.lua> better:).

> >
> Sure, I remember your thoughts regarding checking with constant size and 
> offset.
> 
> I left this for double-checking change proposed in patch.
> 
> I'll leave this as as without changes and will wait review from Sergey
> 
> and then we will decide remove these checks or not.
> 
> >     All of the checks are valid for now, though, so feel free to ignore.

<snipped>

> >     --
> >     Best regards,
> >     Maxim Kokryashkin
> >

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2023-06-06 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  8:09 Sergey Bronnikov via Tarantool-patches
2023-05-30  9:05 ` Maxim Kokryashkin via Tarantool-patches
2023-05-31 14:50   ` Sergey Bronnikov via Tarantool-patches
2023-06-06 12:55     ` Sergey Kaplun via Tarantool-patches [this message]
2023-06-06 12:31 ` Sergey Kaplun via Tarantool-patches
2023-06-06 14:14   ` Sergey Bronnikov via Tarantool-patches
2023-07-04 17:09 ` Igor Munkin 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=ZH8svivoxaDyDHiF@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=estetus@gmail.com \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit v2 1/1] Fix saved bytecode encapsulated in ELF objects.' \
    /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