All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: flush dentry lock drop when sync ocfs2 volume.
Date: Mon, 20 Jul 2009 13:25:24 -0700	[thread overview]
Message-ID: <20090720202524.GB7768@mail.oracle.com> (raw)
In-Reply-To: <20090720190846.GA7768@mail.oracle.com>

On Mon, Jul 20, 2009 at 12:08:46PM -0700, Joel Becker wrote:
> On Mon, Jul 20, 2009 at 02:34:01PM +0200, Jan Kara wrote:
> > +void ocfs2_drop_dl_inodes(struct work_struct *work)
> > +{
> > +	struct ocfs2_super *osb = container_of(work, struct ocfs2_super,
> > +					       dentry_lock_work);
> > +
> > +	__ocfs2_drop_dl_inodes(osb, DL_INODE_DROP_COUNT);
> > +	/*
> > +	 * Don't queue dropping if umount is in progress. We flush the
> > +	 * list in ocfs2_dismount_volume
> > +	 */
> > +	spin_lock(&dentry_list_lock);
> > +	if (osb->dentry_lock_list &&
> > +	    !ocfs2_test_osb_flag(osb, OCFS2_OSB_UMOUNT))
> >  		queue_work(ocfs2_wq, &osb->dentry_lock_work);
> >  	spin_unlock(&dentry_list_lock);
> >  }
> 
> 	The approach is good, but boy, I wish we could use vol_state
> instead of a flag.  We are now tracking the mount/umount state in how
> many places?

	A quick #ocfs2 discussion ensued.  Let's rename OCFS2_OSB_UMOUNT
to OCFS2_OSB_DROP_DENTRY_LOCK_IMMED.  That flag doesn't mean anything
other than the dentry lock behavior, so we'll name it specific to its
purpose.
	I think the rest of the patch looked good, so please resend with
the renamed flag and a clean patch header and I'll verify and apply.

Joel

-- 

Life's Little Instruction Book #20

	"Be forgiving of yourself and others."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2009-07-20 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  9:08 [Ocfs2-devel] [PATCH] ocfs2: flush dentry lock drop when sync ocfs2 volume Tao Ma
2009-07-20 12:34 ` Jan Kara
2009-07-20 14:33   ` Tao Ma
2009-07-20 19:08   ` Joel Becker
2009-07-20 20:25     ` Joel Becker [this message]
2009-07-21  8:58       ` Jan Kara
2009-07-21 19:46         ` Joel Becker
2009-07-21 22:39           ` Jan Kara
2009-07-21 22:49             ` 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=20090720202524.GB7768@mail.oracle.com \
    --to=joel.becker@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.