From: Ulf Hermann <ulf.hermann@qt.io>
To: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: [PATCH 1/2 v2] Don't overflow in __libdw_in_section
Date: Thu, 14 Dec 2017 13:55:00 -0000 [thread overview]
Message-ID: <8b4e21a8-6328-5f05-664c-004d92461ed1@qt.io> (raw)
In-Reply-To: <1513259021.15696.80.camel@klomp.org>
On 12/14/2017 02:43 PM, Mark Wielaard wrote:
> (Meta, I have some trouble applying this with git am, it thinks the
> patch is malformed. But I can apply by hand of course.)
Oh, sorry for that. It's probably the leading spaces again. I keep messing up my mail setup on windows ...
> The transformation seems correct. But if we can overflow/underflow
> here, do we have the same problem in __libdw_offset_in_section where we
> check data->d_size - offset < size, with offset a Dwarf_Off?
Probably we have the same problem there. I didn't catch any instances of it, though.
regards,
Ulf
next prev parent reply other threads:[~2017-12-14 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 15:05 Ulf Hermann
2017-12-14 13:43 ` Mark Wielaard
2017-12-14 13:55 ` Ulf Hermann [this message]
2017-12-20 18:05 ` Mark Wielaard
2017-12-21 13:47 ` Ulf Hermann
2017-12-21 20:22 ` Mark Wielaard
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=8b4e21a8-6328-5f05-664c-004d92461ed1@qt.io \
--to=ulf.hermann@qt.io \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).