bcachefs: Fix "inode not unlinked" error after subvolume deletefor-next

2d33036ca936 introduced a serious bug in subvolume deletion, in a
mistaken attempt to add synchronization that was not needed

We currently don't revoke access to a subvolume being deleted, we
explicitly wait for files in that subvolume to be closed before deleting
it.

6.15 had other subvolume delete fixes which exposed this, leading to
the subvolume root inode being prematurely unlinked.

Currently this only results in dmesg warnings, and is otherwise
harmless, because we verify that the btree says the inode should be
deleted before actually deleting it.

Fixes: 2d33036ca936 ("bcachefs: Fix for 'missing subvolume' error")
Fixes: https://github.com/koverstreet/bcachefs/issues/913
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>

0 files changed, 0 insertions, 0 deletions