[ ssic-linux-Bugs-2009860 ] OpenSSI fails the glibc sha512c-test [ Not a bug ]

"SourceForge.net" <[email protected]>
Newsgroups gmane.linux.cluster.ssic.devel
Message-ID <[email protected]>
Bugs item #2009860, was opened at 2008-07-03 18:19
Message generated for change (Comment added) made by hughesj
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=405834&aid=2009860&group_id=32541

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: John Hughes (hughesj)
Assigned to: Nobody/Anonymous (nobody)
>Summary: OpenSSI fails the glibc sha512c-test [ Not a bug ]

Initial Comment:
This one is strange.  If the glibc test "sha512c-test" is run on a non-initnode it fails.  On the initnode it works.

$ gcc -DTIMEOUNT=10 sha512c-test.c -lcrypt
$ onnode 1 ./a.out
$ echo $?
0
$ onnode 2 ./a.out
Timed out: killed the child process
$ echo $?
1

----------------------------------------------------------------------

>Comment By: John Hughes (hughesj)
Date: 2008-07-04 12:24

Message:
Logged In: YES 
user_id=166336
Originator: YES

Nothing to do with OpenSSI - problem is that my 2nd node, a 2.0GHZ PIV is
too slow to run this test in the 2 seconds allowed!


$ TIMEOUTFACTOR=100 time ./a.out 
2.16user 0.00system 0:02.16elapsed 100%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (0major+155minor)pagefaults 0swaps

$ TIMEOUTFACTOR=100 onnode 1 time ./a.out 
1.50user 0.00system 0:01.54elapsed 97%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (0major+154minor)pagefaults 0swaps



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-07-04 11:02

Message:
Logged In: NO 

Yeah, I get the same behaviour with glibc-2.3.6

I'll keep investigating

----------------------------------------------------------------------

Comment By: Roger Tsang (rogertsang)
Date: 2008-07-04 05:16

Message:
Logged In: YES 
user_id=1246761
Originator: NO

Problem with your glibc?  Can't reproduce this with glibc-2.3.6-0.fc3.1 on
OpenSSI FC3.

1. FC3 glibc doesn't support M_PERTURB.
2. Test fails on any node, but does not timeout.

# ./a.out            
test 0: expected
"$6$saltstring$svn8UoSVapNtMuq1ukKS4tPQd8iKwSMHWjl/O817G3uBnIFNjnQJuesI68u4OTLiBFdcbYEdFCoEOfaS35inz1",
got "$6x9WpaOdMM3g"
test 1: expected
"$6$rounds=10000$saltstringsaltst$OW1/O6BYHV6BcXZu8QVeXbDWra3Oeqh0sbHbbMCVNSnCM/UrjmM0Dp8vOuZeHBy/YTBmSK6H9qs/y3RnOaw5v.",
got "$6x9WpaOdMM3g"
test 2: expected
"$6$rounds=5000$toolongsaltstrin$lQ8jolhgVRVhY4b5pZKaysCLi0QBxGoNeKQzQ3glMhwllF7oGDZxUhx1yxdYcz/e1JSbq3y6JMxxl8audkUEm0",
got "$6x9tL3FIELQY"
test 3: expected
"$6$rounds=1400$anotherlongsalts$POfYwTEok97VWcjxIiSOjiykti.o/pQs.wPvMxQ6Fm7I6IoYN3CmLs66x9t0oSwbtEW7o7UmJEiDwGqd8p4ur1",
got "$6MOs1CNBbb.6"
test 4: expected
"$6$rounds=77777$short$WuQyW2YR.hBNpjjRhpYD/ifIw05xdfeEyQoMxIXbkvr0gge1a1x3yRULJ5CCaUeOxFmtlcGZelFl5CxtgfiAc0",
got "$65OJsZ2gre4c"
test 5: expected
"$6$rounds=123456$asaltof16chars..$BtCwjqMJGx5hrJhZywWvt0RLE8uZ4oPwcelCjmw2kSYu.Ec6ycULevoBK25fs2xXgMNrCzIMVcgEJAstJeonj1",
got "$6lfLcCIGbasI"
test 6: expected
"$6$rounds=1000$roundstoolow$kUMsbe306n21p9R.FRkW3IGn.S9NPN0x50YhH1xhLsPuWGsUSklZt58jaTfF4ZEQpyUNGc0dqbpBYYBaHHrsX.",
got "$69X7GLn2NAcI"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=405834&aid=2009860&group_id=32541

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.