** Changed in: linux (Ubuntu Hirsute)
       Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Impish)
       Status: In Progress => Fix Committed

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

Title:
  ubuntu_ltp / finit_module02 fails on v4.15 and other kernels

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux-oem-5.13 source package in Bionic:
  Invalid
Status in linux-oem-5.14 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.10 source package in Jammy:
  Invalid
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Some uses of kernel_read_file_from_fd may lead to a WARN when the file is
  not opened for reading.

  The WARNING, however, is not present on earlier kernels, which will return
  a different error code. The fix, however, has been applied to upstream stable
  and may be worth so tests can PASS without much change.

  [Fix/Backport]
  The fix is trivial, but the backport for Focal and Bionic was picked up
  from 5.4.y upstream stable tree, because the function was moved to a
  different file.

  [Test case]
  The finit_module02 test case from LTP covers this.

  [Potential regression]
  kernel_read_file_from_fd is used for module loading and kexec, so there is
  where regressions might show up.

  
  =================================================================

  ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS
  (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure
  (5.4.0-1064.67):

  ----
  tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
  finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9)
  finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22)
  finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14)
  finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22)
  finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22)
  tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16)
  finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1)
  tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16)
  finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17)
  finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: 
ETXTBSY (26)
  finit_module02.c:119: TPASS: TestName: directory : EINVAL (22)

  HINT: You _MAY_ be missing kernel fixes, see:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855

  ----

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