ci2 starts bisection 2023-03-28 01:16:03.66730778 +0000 UTC m=+16068.587096653
bisecting fixing commit since 5448b2fda85f2d90de03f053226f721ba2f7e731
building syzkaller on ee50e71ca65deab5f014ff0481809c7b2afa5427
ensuring issue is reproducible on original commit 5448b2fda85f2d90de03f053226f721ba2f7e731

testing commit 5448b2fda85f2d90de03f053226f721ba2f7e731 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 823fb9aee2a3013a9fc70c5725d8ca1aef0aa4b53a2f59ace4e9a436b1f89e5a
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
testing current HEAD fa7bbebb182b97b8a9bfb5bb8babe657b9fd0847
testing commit fa7bbebb182b97b8a9bfb5bb8babe657b9fd0847 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 76011b6d06eb069c2eb20ecfd6c7a618b22df00ae4527a61b96a0490b664f1ef
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
revisions tested: 2, total time: 18m46.415751869s (build: 9m24.4148789s, test: 7m54.231742478s)
the crash still happens on HEAD
commit msg: Merge 5.15.98 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...