From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Mark Zhuang <mark.zhuang@spacemit.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH glibc/release/2.38/master] elf: Remove l_init_called_next field from struct link_map
Date: Wed, 24 Apr 2024 16:23:19 +0200 [thread overview]
Message-ID: <87a5lialgo.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <e6109494-0871-4a6f-900c-ce5b31b64615@linaro.org> (Adhemerval Zanella Netto's message of "Wed, 24 Apr 2024 09:33:36 -0300")
* Adhemerval Zanella Netto:
> On 24/04/24 00:44, Mark Zhuang wrote:
>> From 89639547c9d661446064d50833c2dc00cbbee679 Mon Sep 17 00:00:00 2001
>> From: Mark Zhuang <mark.zhuang@spacemit.com>
>> Date: Wed, 24 Apr 2024 11:16:20 +0800
>> Subject: [PATCH] elf: Remove l_init_called_next field from struct link_map
>>
>> When commit 719866ab2ff0e6d514a04fb47e507d92e70ef7ee revert commit
>> a3189f66a5f2fe86568286fa025fa153be04c6c0, this filed change was
>> missed, now remove it.
>>
>> Reason for remove is same as 719866ab2ff0e6d514a04fb47e507d92e70ef7ee:
>> Incompatibility with existing applications.
>>
>> Signed-off-by: Mark Zhuang <mark.zhuang@spacemit.com>
>
> This patch looks ok, although it is not strictly a backport. Florian,
> any idea why this snippet was not within the dd32e1db386c77c61850a7cbd
> backport?
It was a separate change to preserve internal GLIBC_PRIVATE ABI during
the backport, so that process launch during a concurrent update did not
fail needlessly.
Thanks,
Florian
next prev parent reply other threads:[~2024-04-24 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 3:44 [PATCH glibc/release/2.38/master] elf: Remove l_init_called_next field from struct link_map Mark Zhuang
2024-04-24 12:33 ` Adhemerval Zanella Netto
2024-04-24 14:23 ` Florian Weimer [this message]
2024-04-24 14:39 ` Tom Kacvinsky
-- strict thread matches above, loose matches on Subject: below --
2024-04-24 15:47 mark.zhuang
2024-04-29 14:58 ` Mark Zhuang
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5lialgo.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=mark.zhuang@spacemit.com \
/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).