It was correctly fix-bisected, but then closed as obsolete. If it's indeed fixed, it's expected that it won't happen and will be closed as obsolete soon.
Since we don't systematically handle fix bisection results, I think it's more reasonable to close such bugs as fixed with the commit (at the time it would be currently obsoleted, to give any human moderators time to act).
"WARNING in cow_file_range_inline" report: https://syzkaller.appspot.com/bug?extid=858534c396b0cdd291d2 https://lore.kernel.org/all/0000000000001bde1e05f2bb5be8@google.com/
It was correctly fix-bisected, but then closed as obsolete. If it's indeed fixed, it's expected that it won't happen and will be closed as obsolete soon. Since we don't systematically handle fix bisection results, I think it's more reasonable to close such bugs as fixed with the commit (at the time it would be currently obsoleted, to give any human moderators time to act).