This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809704

Title:
  efivarfs test in ubuntu_kernel_selftest failed on the second run

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==
  If you run the test selftest/efivarfs test suite twice, it will fail on
  the second run.

  This is because the test file created in the first run will obtain the
  immutable property, and it will make the second attempt failed with
  premission denied error.

  == Fix ==
  * 1f0ea958 (selftests: efivarfs: return Kselftest Skip code for skipped tests)
  * dff6d2ae (selftests/efivarfs: clean up test files from test_create*())

  This issue exists in X/B/D, fixed in newer releases.

  For Xenial it lacks the crucial commit which allows the selftest
  framework to handle KSFT_SKIP return code (3f4435b5), so the first
  commit has to be backported to keep using 0 as its return value. The
  second commit is a backport with fuzzy adjustments.

  For Bionic, the first commit is a clean cherry-pick, the second is a
  backport with fuzzy adjustments.

  For Disco, it just needs the second commit, which is also a backport
  with fuzzy adjustments as well.

  == Test ==
  Patch tested against the affected kernels, and it works as expected.

  == Regression Potential ==
  Low, changes limited to testing tools.


  == Original Bug Report ==
  This seems to be an issue to the test case, if you run the test suite twice, 
it will fail on the second run.

  The first run will create the test file:
  $ ll 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27
  -rw------- 1 root root 0 Dec 24 07:16 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27

  This is cause the open(O_WRONLY) test in test_create_read failed with 
premission denied on the second run.
  This issue can be reproduced with upstream kernel tree on Xenial as well.

  $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in efivarfs; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  for TARGET in efivarfs; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  --------------------
  running test_create
  --------------------
  ./efivarfs.sh: line 48: 
/sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: 
Permission denied
    [PASS]
  --------------------
  running test_create_empty
  --------------------
  ./efivarfs.sh: line 65: 
/sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27:
 Permission denied
    [PASS]
  --------------------
  running test_create_read
  --------------------
  open(O_WRONLY): Permission denied
    [FAIL]
  --------------------
  running test_delete
  --------------------
    [PASS]
  --------------------
  running test_zero_size_delete
  --------------------
    [PASS]
  --------------------
  running test_open_unlink
  --------------------
    [PASS]
  --------------------
  running test_valid_filenames
  --------------------
    [PASS]
  --------------------
  running test_invalid_filenames
  --------------------
    [PASS]
  selftests: efivarfs.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Dec 24 05:10 seq
   crw-rw---- 1 root audio 116, 33 Dec 24 05:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [92859.670497] smpboot: CPU 111 is now offline
   [92859.723040] kvm: disabled by bios
   [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d
   [92859.821706] kvm: disabled by bios
  Date: Tue Dec 25 06:30:01 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp.
   Bus 001 Device 002: ID 0000:0001
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware                             1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C620.86B.01.00.0336.112920161700
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WFT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H48104-410
  dmi.chassis.asset.tag: ....................
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...............................
  dmi.chassis.version: ..................
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0336.112920161700:bd11/29/2016:svnIntelCorporation:pnS2600WFT:pvr....................:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...............................:ct23:cvr..................:
  dmi.product.name: S2600WFT
  dmi.product.version: ....................
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809704/+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

Reply via email to