From: Julia Lawall <julia@diku.dk>
To: Mark Fasheh <mfasheh@suse.com>,
Joel Becker <joel.becker@oracle.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: [PATCH 1/2] fs/ocfs2/dlm: Eliminate update of list_for_each_entry loop cursor
Date: Sat, 7 Aug 2010 11:09:13 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1008071108540.5821@ask.diku.dk> (raw)
From: Julia Lawall <julia@diku.dk>
list_for_each_entry uses its first argument to move from one element to the
next, so modifying it can break the iteration.
The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
// <smpl>
@r@
iterator name list_for_each_entry;
expression x,E;
position p1,p2;
@@
list_for_each_entry@p1(x,...) { <... x =@p2 E ...> }
@@
expression x,E;
position r.p1,r.p2;
statement S;
@@
*x =@p2 E
...
list_for_each_entry@p1(x,...) S
// </smpl>
Signed-off-by: Julia Lawall <julia@diku.dk>
---
I don't know whether this is the right solution, but it seems plausible
considering the subsequent test on lock. In any case, setting lock to NULL
and then going back to the top of the loop does not work.
fs/ocfs2/dlm/dlmrecovery.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/ocfs2/dlm/dlmrecovery.c b/fs/ocfs2/dlm/dlmrecovery.c
index 9dfaac7..7084a11 100644
--- a/fs/ocfs2/dlm/dlmrecovery.c
+++ b/fs/ocfs2/dlm/dlmrecovery.c
@@ -1792,10 +1792,10 @@ static int dlm_process_recovery_data(struct dlm_ctxt *dlm,
for (j = DLM_GRANTED_LIST; j <= DLM_BLOCKED_LIST; j++) {
tmpq = dlm_list_idx_to_ptr(res, j);
list_for_each_entry(lock, tmpq, list) {
- if (lock->ml.cookie != ml->cookie)
+ if (lock->ml.cookie != ml->cookie) {
lock = NULL;
- else
break;
+ }
}
if (lock)
break;
next reply other threads:[~2010-08-07 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 9:09 Julia Lawall [this message]
2010-08-12 0:03 ` Joel Becker
2010-08-12 5:46 ` Julia Lawall
2010-08-12 7:14 ` Dan Carpenter
2010-08-12 9:31 ` Joel Becker
2011-11-02 7:39 ` Dan Carpenter
2011-11-02 17:05 ` Sunil Mushran
2011-11-17 8:43 ` [Ocfs2-devel] " 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=Pine.LNX.4.64.1008071108540.5821@ask.diku.dk \
--to=julia@diku.dk \
--cc=joel.becker@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®