ci2 starts bisection 2023-04-27 01:37:44.831405186 +0000 UTC m=+12814.028941877
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: 2ca17c66bda8119df5a1936771ee0406d8033be9671bc2d37747274d9924a722
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
testing current HEAD 14552b29c8fd58d0f78f3fae069a2bbc2432f65b
testing commit 14552b29c8fd58d0f78f3fae069a2bbc2432f65b gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: f82d4216c6486caa6de11a00c826763e257b3593c3fdeb82206c0f54fee7d7e1
all runs: crashed: VFS: Busy inodes after unmount (use-after-free)
revisions tested: 2, total time: 22m2.023893106s (build: 14m32.991319154s, test: 6m54.834873092s)
the crash still happens on HEAD
commit msg: ANDROID: Update .xml file for changes in 5.15.99
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...