public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] support: Replace _SC_MINSIGSTKSZ with _SC_SIGSTKSZ
Date: Sun, 11 Jul 2021 10:44:11 -0400	[thread overview]
Message-ID: <0164a1d6-26b9-ce89-42d5-14336d1796d1@redhat.com> (raw)
In-Reply-To: <CAMe9rOqa-Y=U4OxiSUmWDD86n77g8Ncz5QTTjopBRv8yLnccGA@mail.gmail.com>

On 7/10/21 2:10 PM, H.J. Lu wrote:
> On Fri, Jul 9, 2021 at 3:10 PM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> On 7/9/21 5:38 PM, H.J. Lu via Libc-alpha wrote:
>>> Replace MINSIGSTKSZ with sysconf (_SC_MINSIGSTKSZ) since the constant
>>> MINSIGSTKSZ used in glibc build may be too small.
>>
>> LGTM. It's good to explicitly convert to using sysconf in support/* code.
> 
> I used the wrong _SC_XXX.   _SC_MINSIGSTKSZ is for the empty
> signal handler.   sysconf (_SC_SIGSTKSZ) returns the suggested
> minimum number of bytes of stack space required for a signal stack.
> 
> OK for master?

LGTM. This still goes in the right direction, even if we need more stack
space for testing.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

> From 1b30a2708f2bc8a7161c19737ac5f5927803ffc9 Mon Sep 17 00:00:00 2001
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Date: Sat, 10 Jul 2021 10:56:50 -0700
> Subject: [PATCH] support: Replace _SC_MINSIGSTKSZ with _SC_SIGSTKSZ
> 
> Replace _SC_MINSIGSTKSZ with _SC_SIGSTKSZ since sysconf (_SC_MINSIGSTKSZ)
> returns the minimum number of bytes of free stack space required in order
> to guarantee successful, non-nested handling of a single signal whose
> handler is an empty function while sysconf (_SC_SIGSTKSZ) returns the
> suggested minimum number of bytes of stack space required for a signal
> stack.
> ---
>  support/support_stack_alloc.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/support/support_stack_alloc.c b/support/support_stack_alloc.c
> index b05ae08968..62eee84573 100644
> --- a/support/support_stack_alloc.c
> +++ b/support/support_stack_alloc.c
> @@ -39,10 +39,10 @@ support_stack_alloc (size_t size)
>    if (pagesize == -1)
>      FAIL_EXIT1 ("sysconf (_SC_PAGESIZE): %m\n");
>  
> -  /* Always supply at least sysconf (_SC_MINSIGSTKSZ) space; passing 0
> +  /* Always supply at least sysconf (_SC_SIGSTKSZ) space; passing 0
>       as size means only that much space.  No matter what the number is,
>       round it up to a whole number of pages.  */
> -  size_t stacksize = roundup (size + sysconf (_SC_MINSIGSTKSZ),
> +  size_t stacksize = roundup (size + sysconf (_SC_SIGSTKSZ),
>  			      pagesize);
>  
>    /* The guard bands need to be large enough to intercept offset
> -- 
> 2.31.1
> 


-- 
Cheers,
Carlos.


      reply	other threads:[~2021-07-11 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 21:38 [PATCH] support: Replace MINSIGSTKSZ with sysconf (_SC_MINSIGSTKSZ) H.J. Lu
2021-07-09 22:10 ` Carlos O'Donell
2021-07-10 18:10   ` [PATCH] support: Replace _SC_MINSIGSTKSZ with _SC_SIGSTKSZ H.J. Lu
2021-07-11 14:44     ` Carlos O'Donell [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=0164a1d6-26b9-ce89-42d5-14336d1796d1@redhat.com \
    --to=carlos@redhat.com \
    --cc=hjl.tools@gmail.com \
    --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).