Fix sent to mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112505.html
https://lists.ubuntu.com/archives/kernel-team/2020-August/112506.html
** Description changed:
+ == SRU Justification [ FOCAL ] ==
+
+ The msg_zerocopy.sh kernel self test will fail on machines that don't
+ have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program
+ tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails.
+
+ == Fix ==
+
+ Upstream linux-next commit
+
+ commit 16f6458f2478b55e2b628797bc81a4455045c74e
+ Author: Willem de Bruijn <will...@google.com>
+ Date: Wed Aug 5 04:40:45 2020 -0400
+
+ selftests/net: relax cpu affinity requirement in msg_zerocopy test
+
+ The fix now just emits a warning that CPU affinity can't be set rather
+ than cause an exit(1) termination.
+
+ == Test cast ==
+
+ Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU
+ system. Without the fix the test fails. With the fix it runs
+ successfully as expected.
+
+ == Regression Potential ==
+
+ The original test pinned the CPUs for a benchmarking metric, for our
+ testing we are using this to test to see if the operations in the test
+ work successfully. There is a potential that users using this test will
+ not notice the warning if they are using this test as a benchmark on a 1
+ CPU system and may get more jittery timing in their benchmarks rather
+ than a test failing and complaining they are not running it on a
+ suitable multi-CPU system. However, the likelyhood of a user using this
+ test on a single CPU system for benchmarking is small and as it stands
+ the test will now run and produce potentially jittery benchmarks on a 1
+ CPU system compared to previously where it never ran.
+
+ --------------------
+
This test will return 1
- $ sudo ./msg_zerocopy.sh
+ $ sudo ./msg_zerocopy.sh
ipv4 tcp -t 1
./msg_zerocopy: setaffinity 2
./msg_zerocopy: setaffinity 3
$ echo $?
1
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-13-generic 4.18.0-13.14
ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
AlsaDevices:
- total 0
- crw-rw---- 1 root audio 116, 1 Jan 21 07:41 seq
- crw-rw---- 1 root audio 116, 33 Jan 21 07:41 timer
+ total 0
+ crw-rw---- 1 root audio 116, 1 Jan 21 07:41 seq
+ crw-rw---- 1 root audio 116, 33 Jan 21 07:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Mon Jan 21 07:50:33 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
-
+
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
RelatedPackageVersions:
- linux-restricted-modules-4.18.0-13-generic N/A
- linux-backports-modules-4.18.0-13-generic N/A
- linux-firmware 1.175.1
+ linux-restricted-modules-4.18.0-13-generic N/A
+ linux-backports-modules-4.18.0-13-generic N/A
+ linux-firmware 1.175.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
** Changed in: linux (Ubuntu Eoan)
Status: New => Won't Fix
** Changed in: linux-aws (Ubuntu Eoan)
Status: New => Won't Fix
** Changed in: linux-azure (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812620
Title:
msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-aws package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Status in linux source package in Disco:
Won't Fix
Status in linux-aws source package in Disco:
Won't Fix
Status in linux-azure source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Won't Fix
Status in linux-aws source package in Eoan:
Won't Fix
Status in linux-azure source package in Eoan:
Won't Fix
Status in linux source package in Focal:
New
Status in linux-aws source package in Focal:
New
Status in linux-azure source package in Focal:
New
Bug description:
== SRU Justification [ FOCAL ] ==
The msg_zerocopy.sh kernel self test will fail on machines that don't
have 2 or 3 CPUs such as 1 CPU cloud instances since the C test
program tries to set CPU affinity to CPUs 2 and 3 and bails out if it
fails.
== Fix ==
Upstream linux-next commit
commit 16f6458f2478b55e2b628797bc81a4455045c74e
Author: Willem de Bruijn <will...@google.com>
Date: Wed Aug 5 04:40:45 2020 -0400
selftests/net: relax cpu affinity requirement in msg_zerocopy test
The fix now just emits a warning that CPU affinity can't be set rather
than cause an exit(1) termination.
== Test cast ==
Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU
system. Without the fix the test fails. With the fix it runs
successfully as expected.
== Regression Potential ==
The original test pinned the CPUs for a benchmarking metric, for our
testing we are using this to test to see if the operations in the test
work successfully. There is a potential that users using this test
will not notice the warning if they are using this test as a benchmark
on a 1 CPU system and may get more jittery timing in their benchmarks
rather than a test failing and complaining they are not running it on
a suitable multi-CPU system. However, the likelyhood of a user using
this test on a single CPU system for benchmarking is small and as it
stands the test will now run and produce potentially jittery
benchmarks on a 1 CPU system compared to previously where it never
ran.
--------------------
This test will return 1
$ sudo ./msg_zerocopy.sh
ipv4 tcp -t 1
./msg_zerocopy: setaffinity 2
./msg_zerocopy: setaffinity 3
$ echo $?
1
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-13-generic 4.18.0-13.14
ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jan 21 07:41 seq
crw-rw---- 1 root audio 116, 33 Jan 21 07:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Mon Jan 21 07:50:33 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
RelatedPackageVersions:
linux-restricted-modules-4.18.0-13-generic N/A
linux-backports-modules-4.18.0-13-generic N/A
linux-firmware 1.175.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
