public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31339] arm32 loader crash after cleanup in 2.36 Date: Mon, 05 Feb 2024 14:38:49 +0000 [thread overview] Message-ID: <bug-31339-131-Il8FEGA8qb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31339-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31339 --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- It is indeed a overlook from my patch, previous 49d877a80b29d3002887b084eec6676d9f5fec18 r4 would hold the address of the _SKIP_ARGS which would have a R_ARM_GOTOFF32 relocation, and this would be used later on _dl_start_user to get the _dl_skip_args value after ld.so self-relocate itself. I haven't seen this on my tests because the kernel initializes r4 to 0, so later the 'ld r4, [sl, r4]' will trigger the read of the _GLOBAL_OFFSET_TABLE_. But it does trigger invalid memory access if the kernel, or the simulator, does not ensure that r4 is 0 initialized. I will send a patch to fix it. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-05 14:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-05 11:44 [Bug libc/31339] New: " adrian.ratiu at collabora dot com 2024-02-05 11:48 ` [Bug libc/31339] " adrian.ratiu at collabora dot com 2024-02-05 14:38 ` adhemerval.zanella at linaro dot org [this message] 2024-02-05 15:57 ` adrian.ratiu at collabora dot com 2024-02-05 18:44 ` adhemerval.zanella at linaro dot org
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-31339-131-Il8FEGA8qb@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).