From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Introduce ocfs2_recover_node
Date: Wed, 17 Nov 2010 09:49:34 +0800 [thread overview]
Message-ID: <20101117014934.GC2289@laptop.jp.oracle.com> (raw)
In-Reply-To: <AANLkTinAb5TvZNiYPwP8+L5_m-j-zDs6+zbdCTLW45Jg@mail.gmail.com>
On 10-11-16 16:59, Goldwyn Rodrigues wrote:
<snip>
> @@ -212,8 +198,8 @@ static int ocfs2_recovery_thread_running(struct
> ocfs2_super *osb)
>
> void ocfs2_recovery_exit(struct ocfs2_super *osb)
> {
> - struct ocfs2_recovery_map *rm;
> -
> + struct list_head *iter;
> + struct ocfs2_recover_node *rn;
> /* disable any new recovery threads and wait for any currently
> * running ones to exit. Do this before setting the vol_state. */
> mutex_lock(&osb->recovery_lock);
> @@ -226,75 +212,66 @@ void ocfs2_recovery_exit(struct ocfs2_super *osb)
> * complete. */
> flush_workqueue(ocfs2_wq);
>
> - /*
> - * Now that recovery is shut down, and the osb is about to be
> - * freed, the osb_lock is not taken here.
> - */
> - rm = osb->recovery_map;
> - /* XXX: Should we bug if there are dirty entries? */
> -
> - kfree(rm);
> + spin_lock(&osb->osb_lock);
> + list_for_each(iter, &osb->s_recovery_nodes) {
list_for_each_safe()?
regards,
wengang.
> + rn = list_entry(iter, struct ocfs2_recover_node,
> + rn_list);
> + list_del(&rn->rn_list);
> + }
> + spin_unlock(&osb->osb_lock);
> }
>
next prev parent reply other threads:[~2010-11-17 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 22:59 [Ocfs2-devel] [PATCH 1/2] Introduce ocfs2_recover_node Goldwyn Rodrigues
2010-11-17 1:49 ` Wengang Wang [this message]
2010-11-17 2:00 ` Wengang Wang
2010-11-17 2:04 ` Wengang Wang
-- strict thread matches above, loose matches on Subject: below --
2010-11-17 15:50 Goldwyn Rodrigues
2010-12-02 4:49 ` Sunil Mushran
2010-12-02 5:29 ` Joel Becker
2010-12-02 19:05 ` Sunil Mushran
2010-12-02 23:49 ` Joel Becker
2010-11-12 1:01 Goldwyn Rodrigues
2010-11-12 2:16 ` Wengang Wang
2010-11-12 19:22 ` Goldwyn Rodrigues
2010-11-13 5:03 ` Wengang Wang
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=20101117014934.GC2289@laptop.jp.oracle.com \
--to=wen.gang.wang@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.