public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
	Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: jma14 <jma14@rice.edu>, Carlos O'Donell <carlos@redhat.com>,
	John Mellor-Crummey <johnmc@rice.edu>
Subject: Re: [PATCH v10 1/4] elf: Add la_activity during application exit
Date: Mon, 24 Jan 2022 09:53:07 -0300	[thread overview]
Message-ID: <fd4a3d2a-a885-e03f-dc0f-6cd56b6b5ffb@linaro.org> (raw)
In-Reply-To: <874k5x8irn.fsf@oldenburg.str.redhat.com>



On 21/01/2022 07:50, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
> 
>> +static int
>> +do_test (int argc, char *argv[])
>> +{
>> +  /* We must have either:
>> +     - One our fource parameters left if called initially:
>> +       + path to ld.so         optional
>> +       + "--library-path"      optional
>> +       + the library path      optional
>> +       + the application name  */
>> +  if (restart)
>> +    return handle_restart ();
>> +
>> +  char *spargv[9];
>> +  int i = 0;
>> +  for (; i < argc - 1; i++)
>> +    spargv[i] = argv[i + 1];
>> +  spargv[i++] = (char *) "--direct";
>> +  spargv[i++] = (char *) "--restart";
>> +  spargv[i] = NULL;
> 
> Please add a check for an out-of-range argc value, or allocate the array
> on the heap.

Ack.

> 
>> +  while (xgetline (&buffer, &buffer_length, out))
>> +    {
>> +      if (startswith (buffer, "la_activity: "))
>> +	{
>> +	  uintptr_t cookie;
>> +	  int this_act;
>> +	  int r = sscanf (buffer + strlen ("la_activity: "),
>> +			  "%d %"SCNxPTR"", &this_act, &cookie);
>> +	  TEST_COMPARE (r, 2);
> 
> I wonder if you can fold the startswith check into the sscanf.  At least
> you could put "la_activity: " into the format string.

Ack, I have changed to la_objopen and la_objclose as well.

  reply	other threads:[~2022-01-24 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 21:31 [PATCH v10 0/4] Multiple rtld-audit fixes Adhemerval Zanella
2022-01-17 21:31 ` [PATCH v10 1/4] elf: Add la_activity during application exit Adhemerval Zanella
2022-01-18 11:29   ` Florian Weimer
2022-01-18 13:10     ` Adhemerval Zanella
2022-01-21 10:50       ` Florian Weimer
2022-01-21 10:50   ` Florian Weimer
2022-01-24 12:53     ` Adhemerval Zanella [this message]
2022-01-17 21:31 ` [PATCH v10 2/4] elf: Fix initial-exec TLS access on audit modules (BZ #28096) Adhemerval Zanella
2022-01-18 11:33   ` Florian Weimer
2022-01-18 12:58     ` Adhemerval Zanella
2022-01-18 13:02       ` Florian Weimer
2022-01-18 13:26         ` Adhemerval Zanella
2022-01-18 13:29           ` Florian Weimer
2022-01-18 13:33             ` Adhemerval Zanella
2022-01-18 13:46               ` Adhemerval Zanella
2022-01-18 13:47                 ` Adhemerval Zanella
2022-01-17 21:31 ` [PATCH v10 3/4] elf: Issue la_symbind for bind-now (BZ #23734) Adhemerval Zanella
2022-01-21 11:18   ` Florian Weimer
2022-01-17 21:31 ` [PATCH v10 4/4] elf: Fix runtime linker auditing on aarch64 (BZ #26643) Adhemerval Zanella
2022-01-18 13:36   ` Szabolcs Nagy
2022-01-21 11:19   ` Florian Weimer

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=fd4a3d2a-a885-e03f-dc0f-6cd56b6b5ffb@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=jma14@rice.edu \
    --cc=johnmc@rice.edu \
    --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).