public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30007] New: rfe: dlopen to user buffer or to specified address Date: Mon, 16 Jan 2023 14:13:37 +0000 [thread overview] Message-ID: <bug-30007-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30007 Bug ID: 30007 Summary: rfe: dlopen to user buffer or to specified address Product: glibc Version: unspecified Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: stsp at users dot sourceforge.net Target Milestone: --- I've come to a need of dlopen the solib into the previously mmapped buffer. Currently the load address is chosen in _dl_map_segments(). The elf preferred address is taken, which is usually 0 so any address is used. I can think of 2 possible solutions. One would be to add a new func for DL_AUDIT which passes the needed length to the user and expects an address of a buffer as a return. This will allow the user to mmap the MAP_SHARED buffer if he wants, but the down-side is that ld.so will then need to use read() instead of mmap() to not trash the user's shared mapping. This will likely also need some efforts to implement. Another solution is trivial: just add a new fn dlopen3(file, flags, addr) that provides the base address for dlopen. This will not allow to use the pre-allocated buffer (user doesn't know the needed buffer size at that point) but its trivial to code up and will likely also solve my problem. It was also already requested here by someone else: https://stackoverflow.com/questions/62064806/is-there-a-way-to-specify-the-base-address-of-a-shared-library-using-dlopen What do people think about such an extension? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-01-16 14:13 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 14:13 stsp at users dot sourceforge.net [this message] 2023-01-17 14:17 ` [Bug dynamic-link/30007] " adhemerval.zanella at linaro dot org 2023-01-17 14:35 ` stsp at users dot sourceforge.net 2023-01-19 13:23 ` adhemerval.zanella at linaro dot org 2023-01-19 13:46 ` stsp at users dot sourceforge.net 2023-01-20 6:55 ` [Bug dynamic-link/30007] rfe: dlopen " stsp at users dot sourceforge.net 2023-02-15 16:58 ` stsp at users dot sourceforge.net 2023-03-14 3:20 ` stsp at users dot sourceforge.net 2023-03-14 13:21 ` adhemerval.zanella at linaro dot org 2023-03-15 5:34 ` janderson at rice dot edu 2023-03-15 6:33 ` stsp at users dot sourceforge.net 2023-03-15 10:03 ` stsp at users dot sourceforge.net 2023-03-15 11:05 ` stsp at users dot sourceforge.net 2023-03-15 11:41 ` stsp at users dot sourceforge.net 2023-03-15 12:07 ` stsp at users dot sourceforge.net 2023-03-17 6:44 ` stsp at users dot sourceforge.net 2023-03-18 23:28 ` janderson at rice dot edu 2023-03-19 2:12 ` stsp at users dot sourceforge.net 2023-03-19 2:37 ` stsp at users dot sourceforge.net 2023-03-19 9:47 ` stsp at users dot sourceforge.net 2023-03-19 10:14 ` stsp at users dot sourceforge.net 2023-03-19 13:56 ` stsp at users dot sourceforge.net 2023-03-23 10:34 ` stsp at users dot sourceforge.net 2023-03-27 7:12 ` stsp at users dot sourceforge.net 2023-03-27 17:16 ` janderson at rice dot edu 2023-03-28 1:29 ` stsp at users dot sourceforge.net 2023-03-28 5:02 ` stsp at users dot sourceforge.net 2023-03-28 5:37 ` stsp at users dot sourceforge.net 2023-03-28 6:17 ` janderson at rice dot edu 2023-03-28 9:14 ` stsp at users dot sourceforge.net 2023-03-29 15:26 ` stsp at users dot sourceforge.net 2023-03-31 15:43 ` stsp at users dot sourceforge.net 2023-03-31 15:53 ` stsp at users dot sourceforge.net 2023-03-31 16:08 ` stsp at users dot sourceforge.net 2023-04-03 9:28 ` stsp at users dot sourceforge.net 2023-04-03 9:28 ` stsp at users dot sourceforge.net 2023-04-14 19:09 ` stsp at users dot sourceforge.net 2023-04-14 19:11 ` adhemerval.zanella at linaro dot org 2023-04-14 19:12 ` stsp at users dot sourceforge.net 2023-05-08 14:51 ` stsp at users dot sourceforge.net
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=bug-30007-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).