From: Andreas Gruenbacher <agruenba@xxxxxxxxxx> commit 356b8103d4c495d5440e3e687db9026ec2b76043 upstream. It turns out that the might_sleep() call that commit 660a6126f8c3 adds is triggering occasional data corruption in testing. We're not sure about the root cause yet, but since this commit was added as a debugging aid only, revert it for now. This reverts commit 660a6126f8c3208f6df8d552039cda078a8426d1. Fixes: 660a6126f8c3 ("gfs2: check context in gfs2_glock_put") Cc: stable@xxxxxxxxxxxxxxx # v5.16+ Signed-off-by: Andreas Gruenbacher <agruenba@xxxxxxxxxx> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> --- fs/gfs2/glock.c | 3 --- 1 file changed, 3 deletions(-) --- a/fs/gfs2/glock.c +++ b/fs/gfs2/glock.c @@ -301,9 +301,6 @@ void gfs2_glock_queue_put(struct gfs2_gl void gfs2_glock_put(struct gfs2_glock *gl) { - /* last put could call sleepable dlm api */ - might_sleep(); - if (lockref_put_or_lock(&gl->gl_lockref)) return; Patches currently in stable-queue which might be from agruenba@xxxxxxxxxx are queue-5.16/revert-gfs2-check-context-in-gfs2_glock_put.patch queue-5.16/gfs2-fix-gfs2_release-for-non-writers-regression.patch