ci2 starts bisection 2023-06-07 20:10:46.46116117 +0000 UTC m=+10118.698802679
bisecting fixing commit since 5448b2fda85f2d90de03f053226f721ba2f7e731
building syzkaller on ee50e71ca65deab5f014ff0481809c7b2afa5427
ensuring issue is reproducible on original commit 5448b2fda85f2d90de03f053226f721ba2f7e731

testing commit 5448b2fda85f2d90de03f053226f721ba2f7e731 gcc
compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 84cd4f634bb5f884a8afbf3e305d20070de9e543036ef8e1a2d9ac476946c724
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
testing current HEAD 19c0ed55a470d1cd766484abab04871b648560fb
testing commit 19c0ed55a470d1cd766484abab04871b648560fb gcc
compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: aa34302f710883225248c605ddce6ed1135ecee4e32e711c05a9b0a3f2663c73
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
crash still not fixed/happens on the oldest tested release
revisions tested: 2, total time: 16m6.67761357s (build: 9m36.186199647s, test: 6m6.198988624s)
crash still not fixed on HEAD or HEAD had kernel test errors
commit msg: Merge 5.15.106 into android13-5.15-lts
crash: VFS: Busy inodes after unmount (use-after-free)
VFS: Busy inodes after unmount of ramfs. Self-destruct in 5 seconds.  Have a nice day...