On Thu, May 29, 2025 at 06:34:43PM +0000, Viacheslav Dubeyko wrote: > > diff --git a/fs/hfsplus/extents.c b/fs/hfsplus/extents.c > > index a6d61685ae79..b1699b3c246a 100644 > > --- a/fs/hfsplus/extents.c > > +++ b/fs/hfsplus/extents.c > > @@ -342,9 +342,6 @@ static int hfsplus_free_extents(struct super_block *sb, > > int i; > > int err = 0; > > > > - /* Mapping the allocation file may lock the extent tree */ > > - WARN_ON(mutex_is_locked(&HFSPLUS_SB(sb)->ext_tree->tree_lock)); > > - > > Makes sense to me. Looks good. > > But I really like your mentioning of reproducing the issue in generic/013 and > really nice analysis of the issue there. Sadly, we haven't it in the comment. :) Umm... *Is* that thing safe to call without that lock?
