Skip to content

gfs2: do_xmote fixes

Andreas Gruenbacher gfs2 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3gfs2: finish_xmote cleanupfs/gfs2/glock.c+13 -80 replies
2/3gfs2: do_xmote fixesfs/gfs2/glock.c+25 -190 replies
3/3gfs2: Remove and replace gfs2_glock_queue_workfs/gfs2/glock.c+15 -200 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] gfs2: do_xmote fixes

A closer review of commit 86934198eefa ("gfs2: Clear flags when withdraw prevents xmote") has revealed that this commit got things very wrong and that a more thorough cleanup of function do_xmote() is in order. Here is a set of three patches for doing that:

gfs2: finish_xmote cleanup

Pushes more of the glock spin lock logic into do_xmote() which then allows to simplify things there.

gfs2: Fix do_xmote locking error

The actual do_xmote() fixes and cleanup.

gfs2: Remove and replace gfs2_glock_queue_work

A follow-up cleanup now that the previous patch has eliminated the last user of gfs2_glock_queue_work().

This obsoletes the previous patch "gfs2: Fix do_xmote locking error"
(https://lore.kernel.org/gfs2/[email protected]/).

Thanks,
Andreas

Andreas Gruenbacher (3):
gfs2: finish_xmote cleanup
gfs2: do_xmote fixes
gfs2: Remove and replace gfs2_glock_queue_work

 fs/gfs2/glock.c | 78 ++++++++++++++++++++++++++-----------------------
 1 file changed, 42 insertions(+), 36 deletions(-)
Signature · 1 line
2.44.0