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>,
"v.narang@samsung.com" <v.narang@samsung.com>
Subject: Re: [EDT][PATCH][prelink-cross] dso validation check fix
Date: Fri, 11 Sep 2015 09:09:32 -0500 [thread overview]
Message-ID: <55F2E09C.2060602@windriver.com> (raw)
In-Reply-To: <1402879333.114481430889362699.JavaMail.weblogic@epmlwas03a>
Merged to the staging branch.
On 5/6/15 12:16 AM, Maninder Singh wrote:
> EP-F6AA0618C49C4AEDA73BFF1B39950BAB
> Hi Mark,
>
> dso null pointer check is wrongly placed.
>
>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Signed-off-by: Vaneet Narang <v.narang@samsung.com>
> Reviewed-by: Ajeet Yadav <ajeet.y@samsung.com>
> ---
> trunk/src/rtld/rtld.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/trunk/src/rtld/rtld.c b/trunk/src/rtld/rtld.c
> index 35dfde7..f88ce7f 100644
> --- a/trunk/src/rtld/rtld.c
> +++ b/trunk/src/rtld/rtld.c
> @@ -479,13 +479,13 @@ find_lib_in_path (struct search_path *path, const char *soname,
> if (wrap_access (ret, F_OK) == 0)
> {
> DSO *dso = open_dso (ret);
> + if (dso == NULL)
> + continue;
> int dso_class = gelf_getclass (dso->elf);
> int dso_machine = (dso_class == ELFCLASS32) ?
> elf32_getehdr (dso->elf)->e_machine :
> elf64_getehdr (dso->elf)->e_machine;
>
> - if (dso == NULL)
> - continue;
>
> /* Skip 32-bit libraries when looking for 64-bit. Also
> skip libraries for alternative machines. */
> --
> 1.7.1
>
>
> Thanks and Regards,
> Maninder Singh
>
prev parent reply other threads:[~2015-09-11 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 5:16 [EDT][PATCH][prelink-cross] dso validation check fix Maninder Singh
2015-09-11 14:09 ` 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=55F2E09C.2060602@windriver.com \
--to=mark.hatle@windriver.com \
--cc=ajeet.y@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.