From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH/RFC] sigaltstack02: avoid using MINSIGSTKSZ defined by glibc
Date: Thu, 20 Feb 2014 15:43:23 +0100 [thread overview]
Message-ID: <20140220144323.GA9177@rei> (raw)
In-Reply-To: <956250964.4933831.1392716586384.JavaMail.zimbra@redhat.com>
Hi!
> > The value of MINSIGSTKSZ defined by glibc can be different
> > as the value defined by kernel. Recent change for ppc
> > is now causing sigaltstack02 to fail:
> > https://sourceware.org/ml/libc-alpha/2013-08/msg00093.html
> >
> > Use value which is low enough for all kernel versions.
> >
> > Signed-off-by: Jan Stancek <jstancek@redhat.com>
> > ---
>
> Any thoughts/ideas?
So they fixed the size in glibc which broke the test because the
MINSIGSTKSZ - 1 is not small enough now. I wonder if we can pass
even smaller value (zero) there and get the same result...
Anyway the change looks good to me,
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-02-20 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 9:39 [LTP] [PATCH/RFC] sigaltstack02: avoid using MINSIGSTKSZ defined by glibc Jan Stancek
2014-02-18 9:43 ` Jan Stancek
2014-02-20 14:43 ` chrubis [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=20140220144323.GA9177@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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