From: Mark Hatle <mark.hatle@windriver.com>
To: <maninder1.s@samsung.com>
Cc: AJEET YADAV <ajeet.y@samsung.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
AKHILESH KUMAR <akhilesh.k@samsung.com>,
"v.narang@samsung.com" <v.narang@samsung.com>
Subject: Re: [EDT][prelink-cross] possible memory leak in opd_size
Date: Wed, 9 Sep 2015 17:21:30 -0500 [thread overview]
Message-ID: <55F0B0EA.8080507@windriver.com> (raw)
In-Reply-To: <1484215526.122031430894028615.JavaMail.weblogic@epmlwas03a>
I'm finally getting caught up on these items. I've looked at this, the function
in question is only used on arch-ia64. I don't have any way to test arch-ia64,
nor do I think it's used much anymore (especially in the embedded space). So
I'm going to be skipping this particular patch -- unless someone can convince me
it is the right fix -- or can verify behavior on an IA64 system. (Note, ia64,
not x86-64)
--Mark
On 5/6/15 1:33 AM, Maninder Singh wrote:
> EP-F6AA0618C49C4AEDA73BFF1B39950BAB
>
> Hi,
>
> we found one issue through code-walk through
> and it seems we are creating unusable OPD table , Not sure about fix, please check below fix.
>
> Signed-off-by: Vaneet Narang <v.narang@samsung.com>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Ajeet Yadav <ajeet.y@samsung.com>
> ---
> trunk/src/fptr.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/trunk/src/fptr.c b/trunk/src/fptr.c
> index cfe3aed..39271d5 100644
> --- a/trunk/src/fptr.c
> +++ b/trunk/src/fptr.c
> @@ -458,6 +458,7 @@ opd_size (struct prelink_info *info, GElf_Word entsize)
> e->val = f->val;
> e->gp = f->gp;
> e->opd = ret | OPD_ENT_NEW;
> + f->ent = e;
> ret += entsize;
> }
>
> --
> 1.7.1
>
>
> Thanks and Regards,
> Maninder Singh
>
prev parent reply other threads:[~2015-09-09 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 6:33 [EDT][prelink-cross] possible memory leak in opd_size Maninder Singh
2015-05-06 19:15 ` Mark Hatle
2015-09-09 22:21 ` Mark Hatle [this message]
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=55F0B0EA.8080507@windriver.com \
--to=mark.hatle@windriver.com \
--cc=ajeet.y@samsung.com \
--cc=akhilesh.k@samsung.com \
--cc=maninder1.s@samsung.com \
--cc=v.narang@samsung.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.