From: Rajalakshmi Srinivasaraghavan <rajis@linux.vnet.ibm.com>
To: Manjunath S Matti <mmatti@linux.vnet.ibm.com>,
Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Manjunath Matti via Libc-alpha <libc-alpha@sourceware.org>,
hjl.tools@gmail.com
Subject: Re: [PATCH] powerpc: Use sysconf (_SC_SIGSTKSZ) to set SIGSTKSZ and MINSIGSTKSZ.
Date: Wed, 17 May 2023 17:18:54 -0500 [thread overview]
Message-ID: <b0410a2c-b794-d9d0-587d-8e5ab90d6877@linux.vnet.ibm.com> (raw)
In-Reply-To: <7a0c60f8-092c-b6d7-9e93-0a157511b8dd@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On 5/11/23 11:50 AM, Manjunath S Matti wrote:
>
> On 09/05/23 11:03 pm, Tulio Magno Quites Machado Filho wrote:
>> Manjunath S Matti <mmatti@linux.vnet.ibm.com> writes:
>>
>>> Am I missing some thing, please help me understand the file
>> No. You're right.
>> The issue I hypothesized can't happen.
> Thanks for confirming.
The patch looks good.
>>> I will definitely add a testcases just to check what value are we
>>> getting
>>>
>>> from the kernel.
>> I'm sorry, I'm not sure this test is needed anymore.
>> While it doesn't hurt to have it, it would add little value.
>>
>> Thanks again!
>>
> I have one last thing that I fail to understand, in x86
>
> file: sysdeps/unix/sysv/linux/bits/sigstksz.h
>
> 26 /* Default stack size for a signal handler: sysconf
> (SC_SIGSTKSZ). */
> 27 # undef SIGSTKSZ
> 28 # define SIGSTKSZ sysconf (_SC_SIGSTKSZ)
> 29
> 30 /* Minimum stack size for a signal handler: SIGSTKSZ. */
> 31 # undef MINSIGSTKSZ
> 32 # define MINSIGSTKSZ SIGSTKSZ
>
> line number 32, both MINSIGSTKSZ and SIGSTKSZ are intentionally set to
> the same value.
>
> Do you know why, I just wanted to know the reason behind this.
This was added by commit 6c57d320484988e87e446e2e60ce42816bf51d53.
@H.J. Lu Do you have any comments on this question?
>
> Thank you
>
>
next prev parent reply other threads:[~2023-05-17 22:19 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
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 [this message]
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=b0410a2c-b794-d9d0-587d-8e5ab90d6877@linux.vnet.ibm.com \
--to=rajis@linux.vnet.ibm.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mmatti@linux.vnet.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).