public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Cc: Jeff Xu <jeffxu@google.com>, Florian Weimer <fweimer@redhat.com>,
	"H . J . Lu" <hjl.tools@gmail.com>
Subject: [PATCH v8 5/8] elf: Use RTLD_NODELETE for dependencies
Date: Wed, 29 Jan 2025 14:22:39 -0300	[thread overview]
Message-ID: <20250129172550.1119706-6-adhemerval.zanella@linaro.org> (raw)
In-Reply-To: <20250129172550.1119706-1-adhemerval.zanella@linaro.org>

So dlopen dependencies for objects opened with RTLD_NODELETE
are also marked with RTLD_NODELETE.

Checked on x86_64-linux-gnu.
---
 elf/dl-open.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/elf/dl-open.c b/elf/dl-open.c
index 4c12ddec59..1501428de2 100644
--- a/elf/dl-open.c
+++ b/elf/dl-open.c
@@ -604,7 +604,8 @@ dl_open_worker_begin (void *a)
 
   /* Load that object's dependencies.  */
   _dl_map_object_deps (new, NULL, 0, 0,
-		       mode & (__RTLD_DLOPEN | RTLD_DEEPBIND | __RTLD_AUDIT));
+		       mode & (__RTLD_DLOPEN | RTLD_DEEPBIND | __RTLD_AUDIT
+			       | RTLD_NODELETE));
 
   /* So far, so good.  Now check the versions.  */
   for (unsigned int i = 0; i < new->l_searchlist.r_nlist; ++i)
-- 
2.43.0


  parent reply	other threads:[~2025-01-29 17:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 17:22 [PATCH v8 0/8] Add support for memory sealing Adhemerval Zanella
2025-01-29 17:22 ` [PATCH v8 1/8] linux: Add mseal syscall support Adhemerval Zanella
2025-02-03 18:03   ` Florian Weimer
2025-01-29 17:22 ` [PATCH v8 2/8] elf: Parse gnu properties for static linked binaries Adhemerval Zanella
2025-01-29 17:22 ` [PATCH v8 3/8] elf: Parse gnu properties for the loader Adhemerval Zanella
2025-01-29 17:22 ` [PATCH v8 4/8] rtld: Move call_init_paths after _dl_process_pt_gnu_property Adhemerval Zanella
2025-01-29 17:22 ` Adhemerval Zanella [this message]
2025-01-29 17:22 ` [PATCH v8 6/8] elf: Add support to memory sealing Adhemerval Zanella
2025-01-31 15:43   ` Yury Khrustalev
2025-02-06 19:46   ` Andrei Vagin
2025-01-29 17:22 ` [PATCH v8 7/8] Enable memory sealing automatically Adhemerval Zanella
2025-01-29 17:22 ` [PATCH v8 8/8] linux: Add memory sealing tests Adhemerval Zanella
2025-02-03 18:03 ` [PATCH v8 0/8] Add support for memory sealing Florian Weimer
2025-02-03 18:35   ` Adhemerval Zanella Netto
2025-02-03 19:05     ` Florian Weimer
2025-02-03 19:25       ` Adhemerval Zanella Netto
2025-02-03 19:40         ` Florian Weimer
2025-02-03 20:04           ` Adhemerval Zanella Netto
2025-02-06 14:16             ` Adhemerval Zanella Netto
2025-02-04  2:11           ` Cristian Rodríguez
2025-02-06  9:15             ` Andrei Vagin
2025-02-06 14:25               ` Adhemerval Zanella Netto
2025-02-06 18:03                 ` Aleksandr Mikhalitsyn
2025-02-06 19:47                   ` Adhemerval Zanella Netto
2025-02-07  0:47                     ` Andrei Vagin
2025-02-07 12:10                       ` Adhemerval Zanella Netto
2025-02-07 12:17                         ` Adhemerval Zanella Netto
2025-02-11  8:19             ` Florian Weimer
2025-02-11 17:25               ` Jeff Xu
2025-02-14 20:19 ` Florian Weimer
2025-02-17 16:56   ` Adhemerval Zanella Netto

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=20250129172550.1119706-6-adhemerval.zanella@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=jeffxu@google.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).