Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] validate binary before use
Date: Thu, 31 Jan 2013 14:23:00 -0000	[thread overview]
Message-ID: <510A7E4B.4040608@qnx.com> (raw)
In-Reply-To: <20130130191646.GA1034@host2.jankratochvil.net>

Thanks for the review. Please see some of my comments inlined.

On 13-01-30 02:16 PM, Jan Kratochvil wrote:
> On Tue, 29 Jan 2013 17:15:13 +0100, Aleksandar Ristovski wrote:
>> +	      /* Section vma is unrelocated.  If SO_BASE_ADDR is zero, then
>> +	         use ASECT->VMA as-is.  If not, then use offset + base addr.  */
>> +	      res = target_verify_memory (data, (so_base_addr > 0)?
>
> I do not see why to use target_verify_memory in this case.

While your comment below is correct, I find, since we introduced 
target_verify_memory already, this to be "more correct". Well, it is 
equivalent to what you are suggesting and I was considering doing simply 
read_memory/memcmp here, but then figured, target_verify_memory is more 
semantically correct.

>
> target_verify_memory is there for large sections to compare only their 32-bit
> checksum.  But build-id is already only 20 bytes long, with the protocol
> overhead the 4 vs. 20 bytes do not make a difference.  And it needlessly
> weakens the check, it also does some patching of target_verify_memory.
> Just use target_read_memory and memcmp.

This is all true; however my opinion is that fallback in 
target_verify_memory is correct implementation as it allows using 
target_verify_memory where semantically suitable (like this place IMO) 
regardless of whether actual target implements it or not (e.g. core 
doesn't need to implement it; if it did, the implementation would 
probably be exactly the same as the fallback).

>
>
>> +					   so_base_addr + sect_vma_offset
>> +					   : asect->vma,
>> +					  size);
>
> so->abfd is not properly relocated (not sure why but it is so) but you can

I find that l_addr_inferior remains to be 0 if prelinked object was not 
relocated. I haven't looked at gnu ld, but I would expect it's missing 
to set it correctly (this is misfortunate).

> iterate so->sections..so->sections_end which contains relocated ADDR (=target
> VMA).  Then you can drop the svr4_unrelocated_vma and other calculations
> around.

Ok. I think this is what I tried first but then some testcases would 
fail. Will revisit.


I will be posting new patch with other comments addressed, and please 
provide feedback on the above.


Thanks,

Aleksandar


  reply	other threads:[~2013-01-31 14:23 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 20:21 Aleksandar Ristovski
2012-12-24 19:57 ` Aleksandar Ristovski
2012-12-25  7:37   ` Jan Kratochvil
2012-12-27 20:07     ` Aleksandar Ristovski
2012-12-27 20:59       ` Jan Kratochvil
2012-12-27 21:03         ` Aleksandar Ristovski
2012-12-27 21:13           ` Jan Kratochvil
2012-12-27 21:21             ` Aleksandar Ristovski
2013-01-29 16:15               ` Aleksandar Ristovski
2013-01-30 19:17                 ` Jan Kratochvil
2013-01-31 14:23                   ` Aleksandar Ristovski [this message]
2013-02-01  3:06                     ` Jan Kratochvil
2013-02-01 14:31                       ` Aleksandar Ristovski
2013-02-01 20:43                         ` Jan Kratochvil
2013-02-01 21:32                           ` Aleksandar Ristovski
2013-02-02 12:25                             ` Jan Kratochvil
2013-02-21 21:00                               ` Aleksandar Ristovski
2013-02-21 21:07                                 ` Jan Kratochvil
2013-01-31  6:35                 ` Jan Kratochvil
2013-01-31 14:24                   ` Aleksandar Ristovski
2013-02-22 15:09                     ` Aleksandar Ristovski
2013-02-27 17:42                       ` Aleksandar Ristovski
2013-02-27 18:14                         ` Aleksandar Ristovski
2013-03-22 16:58                         ` Aleksandar Ristovski
2013-03-22 14:45                           ` Aleksandar Ristovski
2013-03-28 20:56                           ` Jan Kratochvil
2013-04-02 17:25                             ` Aleksandar Ristovski
2013-04-02 17:32                               ` Aleksandar Ristovski
2013-04-02 17:45                               ` Jan Kratochvil
2013-04-02 18:02                                 ` Aleksandar Ristovski
2013-04-03 18:52                                   ` Jan Kratochvil
2013-04-04 11:07                                     ` Aleksandar Ristovski
2013-04-04 13:30                                       ` Jan Kratochvil
2013-04-04 17:15                                         ` Aleksandar Ristovski
2013-04-04 18:11                                           ` Aleksandar Ristovski
2013-04-05 13:03                                           ` Jan Kratochvil
2013-04-05 16:08                                             ` Aleksandar Ristovski
2013-04-07  6:06                                               ` Jan Kratochvil
2013-04-08 18:54                                             ` Pedro Alves
2013-04-09  1:15                                               ` Jan Kratochvil
2013-04-05 15:05                                           ` Aleksandar Ristovski
2013-04-07 10:24                                             ` Aleksandar Ristovski
2013-04-08 18:32                                             ` Jan Kratochvil
2013-04-07  5:54                                           ` Jan Kratochvil
2013-04-04  3:16                               ` Jan Kratochvil
2012-12-26 19:24 ` Poenitz Andre
2012-12-27 20:10   ` Aleksandar Ristovski

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=510A7E4B.4040608@qnx.com \
    --to=aristovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox