From: Manjunath S Matti <mmatti@linux.vnet.ibm.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Manjunath Matti via Libc-alpha <libc-alpha@sourceware.org>
Cc: rajis@linux.ibm.com, Manjunath Matti <mmatti@linux.ibm.com>
Subject: Re: [PATCH] powerpc: Use sysconf (_SC_SIGSTKSZ) to set SIGSTKSZ and MINSIGSTKSZ.
Date: Wed, 3 May 2023 21:42:10 +0530 [thread overview]
Message-ID: <7620a9b1-fe92-0764-6011-81d3a19e5590@linux.vnet.ibm.com> (raw)
In-Reply-To: <874jozevbl.fsf@ascii.art.br>
[-- Attachment #1: Type: text/plain, Size: 3102 bytes --]
On 28/04/23 11:35 pm, Tulio Magno Quites Machado Filho wrote:
> Manjunath Matti via Libc-alpha<libc-alpha@sourceware.org> writes:
>
>> Add support in PowerPC to use sysconf (_SC_SIGSTKSZ) to set SIGSTKSZ
>> and MINSIGSTKSZ similar to x86.
> This commit message explains what is being done, but it doesn't make it
> clear why this commit is important.
> If I understand correctly, the goal is to have dynamic values for the
> signal stack size and minimum signal stack size. Is this correct?
Yes that is correct,
file: sysdeps/unix/sysv/linux/dl-parse_auxv.h
52 _dl_random = (void *) auxv_values[AT_RANDOM];
53 GLRO(dl_minsigstacksize) = auxv_values[AT_MINSIGSTKSZ]; <-- gets
the value from kernel.
54 GLRO(dl_sysinfo_dso) = (void *) auxv_values[AT_SYSINFO_EHDR];
> I also suggest to mention the kernel commit ID that started doing this:
> 2896b2dff49d0377e4372f470dcddbcb26f2be59
Yes I will add it.
>> diff --git a/sysdeps/unix/sysv/linux/powerpc/bits/sigstksz.h b/sysdeps/unix/sysv/linux/powerpc/bits/sigstksz.h
>> new file mode 100644
>> index 0000000000..2bec1e7917
>> --- /dev/null
>> +++ b/sysdeps/unix/sysv/linux/powerpc/bits/sigstksz.h
>> @@ -0,0 +1,33 @@
>> +/* Definition of MINSIGSTKSZ and SIGSTKSZ. Linux/PowerPC version.
>> + Copyright (C) 2020-2023 Free Software Foundation, Inc.
> ^ I believe this should be just 2023.
Ack.
>
>> +#if defined __USE_DYNAMIC_STACK_SIZE && __USE_DYNAMIC_STACK_SIZE
>> +# include <unistd.h>
>> +
>> +/* Default stack size for a signal handler: sysconf (SC_SIGSTKSZ). */
>> +# undef SIGSTKSZ
>> +# define SIGSTKSZ sysconf (_SC_SIGSTKSZ)
> I have been told that structs could be using SIGSTKSZ to set their size.
> If that's happening, the softwares using them will stop building after this
> change.
> Is this reasonable?
>
>> +/* Minimum stack size for a signal handler: SIGSTKSZ/4. */
>> +# undef MINSIGSTKSZ
>> +# define MINSIGSTKSZ (SIGSTKSZ >> 2)
>> +#endif
> I didn't understand this part.
> Why SIGSTKSZ/4 ? I know this is correct now, but I think the kernel is
> allowed to use another value.
> Why is this part not using sysconf(_SC_MINSIGSTKSZ)?
> I'm not suggesting to use sysconf() here, but I'm trying to understand
> why the same source of value for both SIGSTKSZ and MINSIGSTKSZ is not
> being used.
In file: sysdeps/unix/sysv/linux/sysconf-sigstksz.h
28 if (minsigstacksize < MINSIGSTKSZ)
29 minsigstacksize = MINSIGSTKSZ;
30 /* MAX (MINSIGSTKSZ, sysconf (_SC_MINSIGSTKSZ)) * 4. */
31 long int sigstacksize = minsigstacksize * 4;
So we are not changing the default implementation.
> If we reach consensus that both macros in this file can have values set
> at runtime, then I it might be worth adding a test in order to check that
> dl_minsigstacksize, MINSIGSTKSZ and AT_MINSIGSTKSZ passed by the kernel
> are identical.
>
There are testcases which already use MINSIGSTKSZ
sysdeps/pthread/tst-signal6.c
signal/tst-minsigstksz-5.c
I will resubmit my patch with the changes I have acknowledged.
Thanks for your time and support.
Manjunath Matti.
next prev parent reply other threads:[~2023-05-03 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:52 Manjunath Matti
2023-04-28 18:05 ` Tulio Magno Quites Machado Filho
2023-05-03 16:12 ` Manjunath S Matti [this message]
2023-05-03 17:48 ` Tulio Magno Quites Machado Filho
2023-05-05 10:15 ` Manjunath S Matti
2023-05-05 14:14 ` Tulio Magno Quites Machado Filho
2023-05-09 12:24 ` Manjunath S Matti
2023-05-09 17:33 ` Tulio Magno Quites Machado Filho
2023-05-11 16:50 ` Manjunath S Matti
2023-05-17 22:18 ` Rajalakshmi Srinivasaraghavan
2023-05-17 23:09 ` H.J. Lu
2023-05-16 11:11 Manjunath Matti
2023-05-24 19:08 ` Florian Weimer
2023-06-23 12:01 ` Manjunath S Matti
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=7620a9b1-fe92-0764-6011-81d3a19e5590@linux.vnet.ibm.com \
--to=mmatti@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=mmatti@linux.ibm.com \
--cc=rajis@linux.ibm.com \
--cc=tuliom@ascii.art.br \
/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).