public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] Fix elf/tst-dl_find_objects with --enable-hardcoded-path-in-tests
Date: Mon, 03 Jan 2022 18:11:02 +0100	[thread overview]
Message-ID: <cover.1641228666.git.fweimer@redhat.com> (raw)

This mini-series reworks the way we we set up l_contiguous for the main
mapping.  This uncovered an oddity in some binaries, tracked as bug
28743.  Due to the oddity, I do not want to assert that the main mapping
is contiguous (on most targets).

Thanks,
Florian

Florian Weimer (3):
  elf: Introduce rtld_setup_main_map
  elf: Set l_contiguous to 1 for the main map in more cases
  elf/tst-dl_find_object: Disable subtests for non-contiguous maps (bug
    28732)

 elf/rtld.c               | 328 ++++++++++++++++++++++-----------------
 elf/tst-dl_find_object.c |  29 ++--
 2 files changed, 201 insertions(+), 156 deletions(-)


base-commit: a51faeee6ae68da63e65eb0a1eb6c9ec2ce2148b
-- 
2.33.1


             reply	other threads:[~2022-01-03 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 17:11 Florian Weimer [this message]
2022-01-03 17:11 ` [PATCH 1/3] elf: Introduce rtld_setup_main_map Florian Weimer
2022-01-16  0:11   ` H.J. Lu
2022-01-03 17:11 ` [PATCH 2/3] elf: Set l_contiguous to 1 for the main map in more cases Florian Weimer
2022-01-16  0:10   ` H.J. Lu
2022-01-03 17:11 ` [PATCH 3/3] elf/tst-dl_find_object: Disable subtests for non-contiguous maps (bug 28732) Florian Weimer
2022-01-14 15:06   ` H.J. Lu
2022-01-14 15:09     ` H.J. Lu
2022-01-14 15:10     ` Florian Weimer
2022-01-14 15:19       ` H.J. Lu
2022-01-14 15:39         ` Florian Weimer
2022-01-14 15:47           ` H.J. Lu
2022-01-14 15:51             ` Florian Weimer
2022-01-14 15:54               ` H.J. Lu
2022-01-14 15:56                 ` Florian Weimer
2022-01-14 16:06                   ` H.J. Lu
2022-01-14 16:12                     ` Florian Weimer
2022-01-16 14:05   ` H.J. Lu

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=cover.1641228666.git.fweimer@redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).