From: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH 2/2] powerpc/signal: Report minimum signal frame size to userspace via AT_MINSIGSTKSZ
Date: Wed, 18 May 2022 09:24:09 -0300 [thread overview]
Message-ID: <87k0ajav12.fsf@linux.ibm.com> (raw)
In-Reply-To: <20220307182734.289289-2-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> Implement the AT_MINSIGSTKSZ AUXV entry, allowing userspace to
> dynamically size stack allocations in a manner forward-compatible with
> new processor state saved in the signal frame
>
> For now these statically find the maximum signal frame size rather than
> doing any runtime testing of features to minimise the size.
>
> glibc 2.34 will take advantage of this, as will applications that use
> use _SC_MINSIGSTKSZ and _SC_SIGSTKSZ.
>
> Cc: Alan Modra <amodra@gmail.com>
> Cc: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
> References: 94b07c1f8c39 ("arm64: signal: Report signal frame size to userspace via auxv")
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Both patches LGTM from a glibc point of view.
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Thanks!
--
Tulio Magno
next prev parent reply other threads:[~2022-05-18 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 18:27 [PATCH 1/2] powerpc/64: Bump SIGSTKSZ and MINSIGSTKSZ Nicholas Piggin
2022-03-07 18:27 ` [PATCH 2/2] powerpc/signal: Report minimum signal frame size to userspace via AT_MINSIGSTKSZ Nicholas Piggin
2022-05-18 12:24 ` Tulio Magno Quites Machado Filho [this message]
2022-05-24 11:08 ` [PATCH 1/2] powerpc/64: Bump SIGSTKSZ and MINSIGSTKSZ Michael Ellerman
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=87k0ajav12.fsf@linux.ibm.com \
--to=tuliom@linux.ibm.com \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 NNTP newsgroup(s).