** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755358
Title:
enosys test in ubuntu_stress_smoke test will terminates the us
With the test triggered yesterday on the same box, the system has passed with
the enosys test:
12:33:56 DEBUG| [stdout] enosys STARTING
12:34:01 DEBUG| [stdout] enosys RETURNED 0
Also the file-ioctl test:
12:34:41 DEBUG| [stdout] file-ioctl STARTING
12:34:46 DEBUG| [stdout] file-ioctl RET
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755358
Title:
e
FIFREEZE fs ioctl disabled for now: http://kernel.ubuntu.com/git/cking
/stress-ng.git/commit/?id=b040ee6da750d407eb0e267ea64347fb5944863f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755358
Title:
File ioctl stressor causes blockage on file system because of ioctl(4,
FIFREEZE) - I will disable that for the moment until we can debug this
one deeper on arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Looks like reboot() and other syscalls were not being rejected, fix
committed:
http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=d0e42d6315403fd35f681275cc32ec1e466d96c0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
BTW, the story is quite different when running this remotely from our jenkins
server with command:
~/kernel-testing/remote ubuntu@ms10-35-mcdivittb0-kernel
--kernel-test-list=ubuntu_stress_smoke_test
It will stuck at the file-ioctl test:
06:46:33 DEBUG| [stdout] fifo PASSED
06:46:33 DEBUG| [s
