David Howells <dhowells@xxxxxxxxxx> wrote: > So: I reran these tests by hand. > (*) fstatfs02 and fstatfs02_64 failed in the unpatched kernel. Works when I run the test manually under the unpatched kernel. Looking back at the saved stdout, I see: fstatfs02 2 TFAIL : unexpected error - 38 : Function not implemented - expected 14 so it may have been run on a filesystem that doesn't support this, but I'm not sure what. > (*) sched_getaffinity01 Works fine now with no modules loaded in the patched kernel. Not sure what the problem was. > and proc01 failed in the patched kernel. I remember now... I killed this during the original run since it seemed to be endlessly redoing: read(10, "\0\0\0\0\0\0\0\6\0\0\0\0\0\0\0\6\0\0\0\0\0\0\0\6\0\0\0\0\0\0\0\6"..., 1024) = 1024 reading /proc/pid/task/tid/pagemap, but it can actually complete if left alone; it just takes ages - it has one 64-bit entry per potential PTE[*] in a process's VM space - and on a 64-bit machine that's a *lot* (~140 quadrillion entries?). > (*) su01 failed in both kernels, but differently. Ah, yes. su01 failed in the original run with 126 because the "expect" program wasn't installed. I install the rpm as soon as I saw it. I should've restarted, I suppose. Now it fails with exit 1 under both kernels because the su01_s1 expect script reports: YOU NEED TO SET ENVIROMENT VARIABLE PASSWD. so that test is faulty. David -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
