]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"
authorHeming Zhao <heming.zhao@suse.com>
Thu, 12 Dec 2024 11:31:05 +0000 (19:31 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 14 Dec 2024 19:04:15 +0000 (20:04 +0100)
commit81d2c5968dba33ccc6e3aee8b2c0cf07c03ba3e1
tree4e4d0bb65383781d3906c98541eb75c1ac92635a
parentd38610a978d68cbc381bbbafb7e6945de24fb188
ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"

This reverts commit dfe6c5692fb5 ("ocfs2: fix the la space leak when
unmounting an ocfs2 volume").

In commit dfe6c5692fb5, the commit log "This bug has existed since the
initial OCFS2 code." is wrong. The correct introduction commit is
30dd3478c3cd ("ocfs2: correctly use ocfs2_find_next_zero_bit()").

The influence of commit dfe6c5692fb5 is that it provides a correct
fix for the latest kernel. however, it shouldn't be pushed to stable
branches. Let's use this commit to revert all branches that include
dfe6c5692fb5 and use a new fix method to fix commit 30dd3478c3cd.

Fixes: dfe6c5692fb5 ("ocfs2: fix the la space leak when unmounting an ocfs2 volume")
Signed-off-by: Heming Zhao <heming.zhao@suse.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ocfs2/localalloc.c