Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various failing tests wrongly assigned to 297 #772

Closed
KenGordon opened this issue Aug 12, 2020 · 4 comments
Closed

Various failing tests wrongly assigned to 297 #772

KenGordon opened this issue Aug 12, 2020 · 4 comments
Labels
needs-triage Bug does not yet have a priority assigned

Comments

@KenGordon
Copy link
Collaborator

Some of the tests which have been enabled as part of fixing 297 (lkl_access_ok) still fail. They will be commented out to be fixed as and when. The comment will be "Enable when sgx-lkl github issue 772 is fixed."

@github-actions github-actions bot added the needs-triage Bug does not yet have a priority assigned label Aug 12, 2020
@KenGordon
Copy link
Collaborator Author

     report/kernel-syscalls-creat-creat06-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-fstatfs-fstatfs02-(debug)-(run-hw)-(8-ethreads).stdout.txt [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-read-read02-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-clock_gettime-clock_gettime02-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-clock_adjtime-clock_adjtime02-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-fremovexattr-fremovexattr02-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-mknod-mknod06-(debug)-(run-hw)-(8-ethreads).stdout.txt    [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-chroot-chroot03-(debug)-(run-hw)-(8-ethreads).stdout.txt  [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-lchown-lchown02-(debug)-(run-hw)-(8-ethreads).stdout.txt  [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-link-link04-(debug)-(run-hw)-(8-ethreads).stdout.txt      [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-clock_settime-clock_settime02-(debug)-(run-hw)-(8-ethreads).stdout.txt
 report/kernel-syscalls-chown-chown04-(debug)-(run-hw)-(8-ethreads).stdout.txt    [ unexpected signal SIGSEGV ] 
 report/kernel-syscalls-chmod-chmod06-(debug)-(run-hw)-(8-ethreads).stdout.txt

@KenGordon
Copy link
Collaborator Author

The chmod one is where a NULL ptr is given as a filename.

@KenGordon
Copy link
Collaborator Author

/kernel/syscalls/chroot/chroot03 - last one
/kernel/syscalls/clock/settime/clock/settime02 - first one
/kernel/syscalls/mknod/mknod06 - second
/kernel/syscalls/chmod/chmod06 - fourth
/kernel/syscalls/clock/gettime/clock/gettime02 - third on (3 sigsegv) all EFAULT ones?
/kernel/syscalls/link/link04 - 6th
/kernel/syscalls/gettimeofday/gettimeofday02 - NA - times out on my box anyway
/kernel/syscalls/fremovexattr/fremovexattr02 - third
/kernel/syscalls/lchown/lchown02 - third
/kernel/syscalls/chown/chown04 - third
/kernel/syscalls/fstatfs/fstatfs02 - second
/kernel/syscalls/clock/adjtime/clock/adjtime02 - sixth
/kernel/syscalls/creat/creat06 - fifth

@davidchisnall
Copy link
Contributor

I've filed #787 to track all of the bugs that have the same root cause. Closing this as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Bug does not yet have a priority assigned
Projects
None yet
Development

No branches or pull requests

2 participants