From: Borislav Petkov <bp@suse.de>
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: tglx@linutronix.de, mingo@kernel.org, luto@kernel.org,
x86@kernel.org, len.brown@intel.com, dave.hansen@intel.com,
hjl.tools@gmail.com, Dave.Martin@arm.com, mpe@ellerman.id.au,
tony.luck@intel.com, ravi.v.shankar@intel.com,
libc-alpha@sourceware.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 4/4] selftest/x86/signal: Include test cases for validating sigaltstack
Date: Fri, 27 Nov 2020 18:32:29 +0100 [thread overview]
Message-ID: <20201127173229.GA13262@zn.tnic> (raw)
In-Reply-To: <20201119190237.626-5-chang.seok.bae@intel.com>
On Thu, Nov 19, 2020 at 11:02:37AM -0800, Chang S. Bae wrote:
> +static void test_sigaltstack(void *altstack, unsigned long size)
> +{
> + if (setup_altstack(altstack, size))
> + err(1, "sigaltstack()");
> +
> + sigalrm_expected = (size > at_minstack_size) ? true : false;
> +
> + sethandler(SIGSEGV, sigsegv, 0);
> + sethandler(SIGALRM, sigalrm, SA_ONSTACK);
> +
> + if (sigsetjmp(jmpbuf, 1) == 0) {
> + printf("[RUN]\tTest an %s sigaltstack\n",
[RUN] Test an enough sigaltstack
That's not english, pls try again.
[OK] SIGALRM signal expectedly delivered.
What is "expectedly delivered"?
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
prev parent reply other threads:[~2020-11-27 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201119190237.626-1-chang.seok.bae@intel.com>
2020-11-19 19:02 ` [PATCH v2 4/4] selftest/x86/signal: Include test cases for validating sigaltstack Chang S. Bae
2020-11-27 17:32 ` Borislav Petkov [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=20201127173229.GA13262@zn.tnic \
--to=bp@suse.de \
--cc=Dave.Martin@arm.com \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=hjl.tools@gmail.com \
--cc=len.brown@intel.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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