From: Peng Haitao <penght@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] setfsuid04.c: the child process should exit 0
Date: Mon, 14 Feb 2011 17:35:34 +0800 [thread overview]
Message-ID: <4D58F766.6040208@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTinXKnOn7XBWJ=+Pc=5r6ObK68s8K2VNEwpuuvBA@mail.gmail.com>
Hi Garrett,
Garrett Cooper said the following on 2011-2-14 14:23:
> How about this version instead? There were issues with the
The two "TEST_ERRNO" should be replaced with "errno" in this version,
If not, the version will fail.
--
Best Regards,
Peng Haitao
> previous version of the file where calling tst_brkm from inside the
> child process would break test execution in interesting and
> non-deterministic ways.
> As a bonus task you could convert things to SAFE_* macros as there
> are a number of spots that I didn't touch that are missing error
> checks.
> Thanks!
> -Garrett
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2011-02-14 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 6:05 [LTP] [PATCH] setfsuid04.c: the child process should exit 0 Peng Haitao
2011-02-14 6:23 ` Garrett Cooper
2011-02-14 9:35 ` Peng Haitao [this message]
2011-02-15 14:42 ` Garrett Cooper
2011-02-16 6:40 ` Peng Haitao
2011-02-16 6:45 ` Garrett Cooper
2011-02-16 7:27 ` Peng Haitao
2011-02-23 9:50 ` Peng Haitao
2011-02-24 5:27 ` Garrett Cooper
2011-02-24 5:27 ` Garrett Cooper
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=4D58F766.6040208@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@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