On Monday 14 April 2008, S.Çağlar Onur wrote: > Compiling LTP with "-fstack-protector -D_FORTIFY_SOURCE=2" ends up with > some test failures like following;
each case will have to be analyzed individually to make sure the test is doing
what we expect. we often pass bad pointers and values and such *on purpose*
to make sure the POSIX interfaces are working properly. building things with
SSP and fortification will simply get in the way.
> And even after some time machine goes down and hard reboot neeeded,
> following output is failed tests list but machine freezes before LTP
> completes its tests so i'm not sure which test causes lockup.
you either got fork bombed (or similar resource starvation), or LTP is doing
its job and finding non-robustness in the system which needs to be fixed.
nothing in userspace should be able to take down the system.
i actually dont think most (any?) of the LTP tests need to be run as root ...
perhaps Subrata can comment on that. we should probably have an LTP function
for test cases that require root which we can call at the start of the
function ... so in our test cases we call like:
ltp_require_root();
and in the library we have like:
void ltp_require_root(void)
{
if (getuid()) {
tst_resm(TWARN, "%s: test requires root, skipping\n", TCID);
tst_exit();
}
}
-mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
