** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Description changed:
+ SRU Justification:
+
+ [Impact]
+ On Jammy 6.8 series, ioprio_set system call does not return correct error
value when setting IOPRIO_CLASS_BE to an invalid value.
+
+ [Fix]
+ Partially reverting commit <> workaround the issue.
+
+ [Test Plan]
+ Run LTP syscall testsuite `ioprio_set03` can sufficiently test the fix.
+
+ [Where problems could occur]
+ The patch could damage the ioprio_set system call handling further and cause
issues with user-space applications that set the I/O priorities.
+
+ [Other Info]
+ Original bug report:
+
Test failed with 6.5.0-1002.2.
Test output:
<<<test_start>>>
tag=ioprio_set03 stime=1692085364
cmdline="ioprio_set03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
ioprio_set03.c:39: TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work
ioprio_set03.c:47: TINFO: tested illegal priority with class NONE
ioprio_set03.c:50: TPASS: returned correct error for wrong prio: EINVAL (22)
Summary:
passed 1
failed 1
broken 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
Test case:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioprio/ioprio_set03.c
** Description changed:
SRU Justification:
[Impact]
On Jammy 6.8 series, ioprio_set system call does not return correct error
value when setting IOPRIO_CLASS_BE to an invalid value.
[Fix]
- Partially reverting commit <> workaround the issue.
+ Partially reverting the upstream commit
eca2040972b411ec27483bf75dc8b84e730e88ff can workaround the issue.
[Test Plan]
Run LTP syscall testsuite `ioprio_set03` can sufficiently test the fix.
[Where problems could occur]
The patch could damage the ioprio_set system call handling further and cause
issues with user-space applications that set the I/O priorities.
[Other Info]
Original bug report:
Test failed with 6.5.0-1002.2.
Test output:
<<<test_start>>>
tag=ioprio_set03 stime=1692085364
cmdline="ioprio_set03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
ioprio_set03.c:39: TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work
ioprio_set03.c:47: TINFO: tested illegal priority with class NONE
ioprio_set03.c:50: TPASS: returned correct error for wrong prio: EINVAL (22)
Summary:
passed 1
failed 1
broken 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
Test case:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioprio/ioprio_set03.c
** Description changed:
SRU Justification:
[Impact]
On Jammy 6.8 series, ioprio_set system call does not return correct error
value when setting IOPRIO_CLASS_BE to an invalid value.
+
+ On Ubuntu Jammy, since we are using linux-klibc-dev package from 5.15 kernel
+ the new ioprio level checking logic (added in upstream commit
893e5d32d5832674bcf6465f27958e883b72b346) resided in the 6.8 linux-klibc-dev
headers
+ will not be triggered.
[Fix]
Partially reverting the upstream commit
eca2040972b411ec27483bf75dc8b84e730e88ff can workaround the issue.
[Test Plan]
Run LTP syscall testsuite `ioprio_set03` can sufficiently test the fix.
[Where problems could occur]
The patch could damage the ioprio_set system call handling further and cause
issues with user-space applications that set the I/O priorities.
[Other Info]
Original bug report:
Test failed with 6.5.0-1002.2.
Test output:
<<<test_start>>>
tag=ioprio_set03 stime=1692085364
cmdline="ioprio_set03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
ioprio_set03.c:39: TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work
ioprio_set03.c:47: TINFO: tested illegal priority with class NONE
ioprio_set03.c:50: TPASS: returned correct error for wrong prio: EINVAL (22)
Summary:
passed 1
failed 1
broken 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
Test case:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioprio/ioprio_set03.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2031382
Title:
ioprio_set03 in ubuntu_ltp_syscalls failed with J-oem-6.5 (TFAIL:
ioprio_set IOPRIO_CLASS_BE prio 8 should not work)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031382/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
