From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Carlos O'Donell <carlos@redhat.com>,
libc-alpha@sourceware.org, jma14 <jma14@rice.edu>
Cc: John Mellor-Crummey <johnmc@rice.edu>, Ben Woodard <woodard@redhat.com>
Subject: Re: [PATCH v11 1/4] elf: Add la_activity during application exit
Date: Tue, 25 Jan 2022 00:06:51 -0300 [thread overview]
Message-ID: <978ef9e9-a0bc-a9ad-0675-6b7c3c706742@linaro.org> (raw)
In-Reply-To: <9a2bd363-d48e-6e20-0bd2-a7e374c6e3cd@redhat.com>
On 24/01/2022 18:47, Carlos O'Donell wrote:
> On 1/24/22 08:46, Adhemerval Zanella wrote:
>> la_activity is not called during application exit, even though
>> la_objclose is.
>
> This fails on my x86_64 tester.
>
> tst-audit23.c:150: numeric comparison failure
> left: 140392013825880 (0x7faf901d0758); from: cookie
> right: 18446744073709551615 (0xffffffffffffffff); from: last_act_cookie
> tst-audit23.c:150: numeric comparison failure
> left: 140392013825880 (0x7faf901d0758); from: cookie
> right: 18446744073709551615 (0xffffffffffffffff); from: last_act_cookie
> tst-audit23.c:150: numeric comparison failure
> left: 93825010503032 (0x5555566c0d78); from: cookie
> right: 18446744073709551615 (0xffffffffffffffff); from: last_act_cookie
> tst-audit23.c:145: numeric comparison failure
> left: 2 (0x2); from: acts[nacts]
> right: 140392013825880 (0x7faf901d0758); from: cookie
> tst-audit23.c:214: numeric comparison failure
> left: 2 (0x2); from: last_act_cookie
> right: 140392013825880 (0x7faf901d0758); from: cookie
> tst-audit23.c:132: numeric comparison failure
> left: 2 (0x2); from: last_act
> right: 0 (0x0); from: LA_ACT_CONSISTENT
> tst-audit23.c:150: numeric comparison failure
> left: 140392013825880 (0x7faf901d0758); from: cookie
> right: 2 (0x2); from: last_act_cookie
> error: 7 test failures
>
> Reproduces with:
> make test t=elf/tst-audit23
>
> Tester is using: "--enable-hardcoded-path-in-tests" to exercise slightly
> different testing paths.
I really can't reproduce it neither on x86_64 nor on i686 with both
gcc 11 and 12. And the buildbot also did not trigger any failure.
I checked with both with and without --enable-hardcoded-path-in-tests,
and also on aarch64 and powerpc64le.
So maybe is it something in your environment?
next prev parent reply other threads:[~2022-01-25 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 13:46 [PATCH v11 0/4] Multiple rtld-audit fixes Adhemerval Zanella
2022-01-24 13:46 ` [PATCH v11 1/4] elf: Add la_activity during application exit Adhemerval Zanella
2022-01-24 21:47 ` Carlos O'Donell
2022-01-25 3:06 ` Adhemerval Zanella [this message]
2022-01-25 18:27 ` Adhemerval Zanella
2022-01-24 13:46 ` [PATCH v11 2/4] elf: Fix initial-exec TLS access on audit modules (BZ #28096) Adhemerval Zanella
2022-01-24 13:46 ` [PATCH v11 3/4] elf: Issue la_symbind for bind-now (BZ #23734) Adhemerval Zanella
2022-01-24 13:46 ` [PATCH v11 4/4] elf: Fix runtime linker auditing on aarch64 (BZ #26643) Adhemerval Zanella
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=978ef9e9-a0bc-a9ad-0675-6b7c3c706742@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=jma14@rice.edu \
--cc=johnmc@rice.edu \
--cc=libc-alpha@sourceware.org \
--cc=woodard@redhat.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).