From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2_cluster_lock: code cleanup for redundant assignment
Date: Thu, 07 May 2009 11:50:37 -0700 [thread overview]
Message-ID: <4A032D7D.5040600@oracle.com> (raw)
In-Reply-To: <4A0328DC.6050702@suse.de>
While this patch may be correct, we have to take into consideration
that we have to backport patches to 1.4, etc. In that light, is this
patch worth it?
Coly Li wrote:
> In fs/ocfs2/dlmglue.c:ocfs2_cluster_lock(), after label 'out:' the code is:
>
> 1373 if (wait && arg_flags & OCFS2_LOCK_NONBLOCK &&
> 1374 mw.mw_mask & (OCFS2_LOCK_BUSY|OCFS2_LOCK_BLOCKED)) {
> 1375 wait = 0;
> 1376 if (lockres_remove_mask_waiter(lockres, &mw))
> 1377 ret = -EAGAIN;
> 1378 else
> 1379 goto again;
> 1380 }
>
> On L1375 variable 'wait' is assigned to 0. But if execution path goes to L1379
> and jumps to label 'again:' on L1262, there is already an assignment to 'wait'
> on L1263:
>
> 1262 again:
> 1263 wait = 0;
> 1264
>
> The previous 'wait = 0' on L1375 is redundant in this case. This patch removes
> such a redundant variable assignment.
>
> Signed-off-by: Coly Li <coly.li@suse.de>
> ---
> fs/ocfs2/dlmglue.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
> index e15fc7d..b6060e3 100644
> --- a/fs/ocfs2/dlmglue.c
> +++ b/fs/ocfs2/dlmglue.c
> @@ -1372,10 +1372,10 @@ out:
> */
> if (wait && arg_flags & OCFS2_LOCK_NONBLOCK &&
> mw.mw_mask & (OCFS2_LOCK_BUSY|OCFS2_LOCK_BLOCKED)) {
> - wait = 0;
> - if (lockres_remove_mask_waiter(lockres, &mw))
> + if (lockres_remove_mask_waiter(lockres, &mw)) {
> + wait = 0;
> ret = -EAGAIN;
> - else
> + } else
> goto again;
> }
> if (wait) {
>
next prev parent reply other threads:[~2009-05-07 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 18:30 [Ocfs2-devel] [PATCH] ocfs2_cluster_lock: code cleanup for redundant assignment Coly Li
2009-05-07 18:50 ` Sunil Mushran [this message]
2009-05-08 6:03 ` Coly Li
2009-05-07 19:08 ` Joel Becker
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=4A032D7D.5040600@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.