canonical-ubuntu-qa team mailing list archive

Thread
Date
[Bug 2088422] [NEW] fanotify22 from ubuntu_ltp_syscalls failed with J-5.15.0-127.137

To: canonical-ubuntu-qa@xxxxxxxxxxxxxxxxxxx
From: Po-Hsu Lin <2088422@xxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Nov 2024 06:47:15 -0000
Reply-to: Bug 2088422 <2088422@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx
Public bug reported:

Issue found with Jammy 5.15.0-127.137

Test passed with 5.15.0-125-generic

Test log:
<<<test_start>>>
tag=fanotify22 stime=1731911133
cmdline="fanotify22"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_tmpdir.c:316: TINFO: Using /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H as tmpdir (ext2/ext3/ext4 filesystem)
tst_device.c:96: TINFO: Found free device 3 '/dev/loop3'
tst_test.c:1158: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts=''
mke2fs 1.46.5 (30-Dec-2021)
tst_test.c:1170: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
tst_test.c:1860: TINFO: LTP version: 20240930
tst_test.c:1864: TINFO: Tested kernel: 5.15.0-127-generic #137-Ubuntu SMP Fri Nov 8 15:21:01 UTC 2024 x86_64
tst_test.c:1703: TINFO: Timeout per run is 0h 00m 30s
fanotify.h:122: TINFO: fid(test_mnt/internal_dir/bad_dir) = f50b391d.7b6964c6.d.481fd95d.0...
fanotify.h:122: TINFO: fid(test_mnt/internal_dir) = f50b391d.7b6964c6.c.6280452c.0...
fanotify22.c:278: TINFO: Umounting /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt
debugfs 1.46.5 (30-Dec-2021)
debugfs 1.46.5 (30-Dec-2021)
fanotify22.c:281: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
fanotify.h:122: TINFO: fid(test_mnt) = f50b391d.7b6964c6.2.0.0...
fanotify22.c:59: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=21
fanotify22.c:59: TBROK: mount(/dev/loop3, test_mnt, ext4, 33, 0x5607078181b1) failed: EROFS (30)

HINT: You _MAY_ be missing kernel fixes:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=124e7c61deb2

Summary:
passed   0
failed   0
broken   1
skipped  0
warnings 0

This can be reproduced with the latest LTP (commit ec41611) as well.

Investigation shows this is probably because of commit d3476f3d "ext4:
don't set SB_RDONLY after filesystem errors" applied to Jammy tree via
stable update (bug 2086242)

https://lore.kernel.org/linux-ext4/20241004221556.19222-1-jack@xxxxxxx/
is a potential fix for this issue.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Jammy)
     Importance: Undecided
         Status: New


** Tags: 5.15 jammy sru-20241028 ubuntu-ltp-syscalls

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Description changed:

  Issue found with Jammy 5.15.0-127.137
  
  Test passed with 5.15.0-125-generic
  
  Test log:
  <<<test_start>>>
  tag=fanotify22 stime=1731911133
  cmdline="fanotify22"
  contacts=""
  analysis=exit
  <<<test_output>>>
  incrementing stop
  tst_tmpdir.c:316: TINFO: Using /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H as tmpdir (ext2/ext3/ext4 filesystem)
  tst_device.c:96: TINFO: Found free device 3 '/dev/loop3'
  tst_test.c:1158: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts=''
  mke2fs 1.46.5 (30-Dec-2021)
  tst_test.c:1170: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
  tst_test.c:1860: TINFO: LTP version: 20240930
  tst_test.c:1864: TINFO: Tested kernel: 5.15.0-127-generic #137-Ubuntu SMP Fri Nov 8 15:21:01 UTC 2024 x86_64
  tst_test.c:1703: TINFO: Timeout per run is 0h 00m 30s
  fanotify.h:122: TINFO: fid(test_mnt/internal_dir/bad_dir) = f50b391d.7b6964c6.d.481fd95d.0...
  fanotify.h:122: TINFO: fid(test_mnt/internal_dir) = f50b391d.7b6964c6.c.6280452c.0...
  fanotify22.c:278: TINFO: Umounting /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt
  debugfs 1.46.5 (30-Dec-2021)
  debugfs 1.46.5 (30-Dec-2021)
  fanotify22.c:281: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
  fanotify.h:122: TINFO: fid(test_mnt) = f50b391d.7b6964c6.2.0.0...
  fanotify22.c:59: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=21
  fanotify22.c:59: TBROK: mount(/dev/loop3, test_mnt, ext4, 33, 0x5607078181b1) failed: EROFS (30)
  
  HINT: You _MAY_ be missing kernel fixes:
  
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=124e7c61deb2
  
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  
+ This can be reproduced with the latest LTP (commit ec41611) as well.
+ 
  Investigation shows this is probably because of commit d3476f3d "ext4:
  don't set SB_RDONLY after filesystem errors" applied to Jammy tree via
  stable update (bug 2086242)
  
  https://lore.kernel.org/linux-ext4/20241004221556.19222-1-jack@xxxxxxx/
  is a potential fix for this issue.

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2088422

Title:
  fanotify22 from ubuntu_ltp_syscalls failed with J-5.15.0-127.137

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New

Bug description:
  Issue found with Jammy 5.15.0-127.137

  Test passed with 5.15.0-125-generic

  Test log:
  <<<test_start>>>
  tag=fanotify22 stime=1731911133
  cmdline="fanotify22"
  contacts=""
  analysis=exit
  <<<test_output>>>
  incrementing stop
  tst_tmpdir.c:316: TINFO: Using /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H as tmpdir (ext2/ext3/ext4 filesystem)
  tst_device.c:96: TINFO: Found free device 3 '/dev/loop3'
  tst_test.c:1158: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts=''
  mke2fs 1.46.5 (30-Dec-2021)
  tst_test.c:1170: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
  tst_test.c:1860: TINFO: LTP version: 20240930
  tst_test.c:1864: TINFO: Tested kernel: 5.15.0-127-generic #137-Ubuntu SMP Fri Nov 8 15:21:01 UTC 2024 x86_64
  tst_test.c:1703: TINFO: Timeout per run is 0h 00m 30s
  fanotify.h:122: TINFO: fid(test_mnt/internal_dir/bad_dir) = f50b391d.7b6964c6.d.481fd95d.0...
  fanotify.h:122: TINFO: fid(test_mnt/internal_dir) = f50b391d.7b6964c6.c.6280452c.0...
  fanotify22.c:278: TINFO: Umounting /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt
  debugfs 1.46.5 (30-Dec-2021)
  debugfs 1.46.5 (30-Dec-2021)
  fanotify22.c:281: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=0
  fanotify.h:122: TINFO: fid(test_mnt) = f50b391d.7b6964c6.2.0.0...
  fanotify22.c:59: TINFO: Mounting /dev/loop3 to /tmp/ltp-d9TOV3nQhh/LTP_fanU1bb4H/test_mnt fstyp=ext4 flags=21
  fanotify22.c:59: TBROK: mount(/dev/loop3, test_mnt, ext4, 33, 0x5607078181b1) failed: EROFS (30)

  HINT: You _MAY_ be missing kernel fixes:

  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=124e7c61deb2

  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0

  This can be reproduced with the latest LTP (commit ec41611) as well.

  Investigation shows this is probably because of commit d3476f3d "ext4:
  don't set SB_RDONLY after filesystem errors" applied to Jammy tree via
  stable update (bug 2086242)

  https://lore.kernel.org/linux-
  ext4/20241004221556.19222-1-jack@xxxxxxx/ is a potential fix for this
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2088422/+subscriptions
Follow ups

[Bug 2088422] Re: fanotify22 from ubuntu_ltp_syscalls failed with J-5.15.0-127.137
From: Po-Hsu Lin, 2024-11-18