From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 02/12] GFS2: Eliminate a goto in finish_xmote
Date: Mon, 9 Jul 2018 12:50:18 -0500 [thread overview]
Message-ID: <20180709175028.17090-3-rpeterso@redhat.com> (raw)
In-Reply-To: <20180709175028.17090-1-rpeterso@redhat.com>
This is another baby step toward a better glock state machine.
This patch eliminates a goto in function finish_xmote so we can
begin unraveling the cryptic logic with later patches.
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
fs/gfs2/glock.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index 8d0c467f8c9a..8f2721515ff5 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -472,11 +472,11 @@ static void finish_xmote(struct gfs2_glock *gl, unsigned int ret)
list_move_tail(&gh->gh_list, &gl->gl_holders);
gh = find_first_waiter(gl);
gl->gl_target = gh->gh_state;
- goto retry;
- }
- /* Some error or failed "try lock" - report it */
- if ((ret & LM_OUT_ERROR) ||
- (gh->gh_flags & (LM_FLAG_TRY | LM_FLAG_TRY_1CB))) {
+ state = LM_ST_UNLOCKED;
+ } else if ((ret & LM_OUT_ERROR) ||
+ (gh->gh_flags & (LM_FLAG_TRY |
+ LM_FLAG_TRY_1CB))) {
+ /* An error or failed "try lock" - report it */
gl->gl_target = gl->gl_state;
do_error(gl, ret);
goto out;
@@ -485,7 +485,6 @@ static void finish_xmote(struct gfs2_glock *gl, unsigned int ret)
switch(state) {
/* Unlocked due to conversion deadlock, try again */
case LM_ST_UNLOCKED:
-retry:
do_xmote(gl, gl->gl_target);
break;
/* Conversion fails, unlock and try again */
--
2.17.1
next prev parent reply other threads:[~2018-07-09 17:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 17:50 [Cluster-devel] [GFS2 PATCH 00/12] Radical Reform of glock state machine Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 01/12] GFS2: Make do_xmote determine its own gh parameter Bob Peterson
2018-07-09 17:50 ` Bob Peterson [this message]
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 03/12] GFS2: Baby step toward a real state machine: finish_xmote Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 04/12] GFS2: Add do_xmote states to state machine Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 05/12] GFS2: Make do_xmote not call the state machine again Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 06/12] GFS2: Add blocking and non-blocking demote to state machine Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 07/12] GFS2: Add a new GL_ST_PROMOTE state to glock " Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 08/12] GFS2: Replace run_queue with new GL_ST_RUN state in " Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 09/12] GFS2: Reduce redundancy in GL_ST_DEMOTE_NONBLOCK state Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 10/12] GFS2: Reduce glock_work_func to a single call to state_machine Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 11/12] GFS2: Add new GL_ST_UNLOCK state to reduce calls to the __ version Bob Peterson
2018-07-09 17:50 ` [Cluster-devel] [GFS2 PATCH 12/12] GFS2: Optimization of GL_ST_UNLOCK state Bob Peterson
2018-07-10 8:27 ` [Cluster-devel] [GFS2 PATCH 00/12] Radical Reform of glock state machine Steven Whitehouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180709175028.17090-3-rpeterso@redhat.com \
--to=rpeterso@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).