public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 3/3] elf: Always call destructors in reverse constructor order
Date: Tue, 22 Aug 2023 12:46:28 +0200	[thread overview]
Message-ID: <87bkez4anv.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <2a10bdb3-88ff-0313-a17e-0a0a8e8aa5fb@linaro.org> (Adhemerval Zanella's message of "Tue, 15 Feb 2022 08:59:23 -0300")

* Adhemerval Zanella:

>>  #ifdef SHARED
>> -  int do_audit = 0;
>> - again:
>> +  int last_pass = GLRO(dl_naudit) > 0;
>> +  Lmid_t last_ns = -1;	     /* Avoid some LA_ACT_DELETE callouts.  */
>
> This has caused as lot of audit regressions, since it will make
> _dl_audit_activity_nsid access
>
>   struct link_map *head = GL(dl_ns)[-1]._ns_loaded;

>> -	  _dl_audit_activity_nsid (ns, LA_ACT_DELETE);
>> +	if (GL(dl_ns)[l->l_ns]._ns_loaded->l_auditing != do_audit)
>> +	  continue;
>> +
>> +	if (last_ns != l->l_ns)
>> +	  {
>
> I think you will need a
>
>    if (last_ns != -1)
>      _dl_audit_activity_nsid (last_ns, LA_ACT_CONSISTENT);

Thanks, somehow I missed your comment.  I will resend a v3.

Florian


      reply	other threads:[~2023-08-22 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 15:17 [PATCH v2 0/3] Predictable ELF destructor ordering Florian Weimer
2022-02-03 15:17 ` [PATCH v2 1/3] elf: Do not rely on relocation dependencies for destructor sorting Florian Weimer
2022-02-14 20:11   ` Adhemerval Zanella
2022-02-03 15:18 ` [PATCH v2 2/3] elf: Do not run constructors for proxy objects Florian Weimer
2022-02-03 15:18 ` [PATCH v2 3/3] elf: Always call destructors in reverse constructor order Florian Weimer
2022-02-15 11:59   ` Adhemerval Zanella
2023-08-22 10:46     ` Florian Weimer [this message]

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=87bkez4anv.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).