From: "J. Bruce Fields" <bfields@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: rename locking
Date: Wed, 30 May 2012 21:50:10 -0400 [thread overview]
Message-ID: <1338429016-20119-1-git-send-email-bfields@redhat.com> (raw)
This is a resend of the rename locking patches. With the quota locking
cleaned up, it looks safe to move ext4's locking into common code and
then use that.
Steven Whitehouse has another plan for gfs2, but last I talked to him
was OK with Jan Kara's fix for now.
--b.
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: rename locking
Date: Wed, 30 May 2012 21:50:10 -0400 [thread overview]
Message-ID: <1338429016-20119-1-git-send-email-bfields@redhat.com> (raw)
This is a resend of the rename locking patches. With the quota locking
cleaned up, it looks safe to move ext4's locking into common code and
then use that.
Steven Whitehouse has another plan for gfs2, but last I talked to him
was OK with Jan Kara's fix for now.
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-05-31 1:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 1:50 J. Bruce Fields [this message]
2012-05-31 1:50 ` rename locking J. Bruce Fields
2012-05-31 1:50 ` [PATCH 1/6] gfs2: Get rid of I_MUTEX_QUOTA usage J. Bruce Fields
2012-05-31 7:50 ` Steven Whitehouse
2012-05-31 7:50 ` Steven Whitehouse
2012-05-31 12:14 ` Bob Peterson
2012-05-31 1:50 ` [PATCH 2/6] vfs: fix outdated i_mutex_lock_class documentation J. Bruce Fields
2012-05-31 1:50 ` J. Bruce Fields
2012-05-31 18:51 ` Jan Kara
2012-05-31 18:51 ` Jan Kara
2012-05-31 18:54 ` Jan Kara
2012-05-31 18:54 ` Jan Kara
2012-05-31 20:11 ` J. Bruce Fields
2012-05-31 20:11 ` J. Bruce Fields
2012-05-31 20:14 ` [PATCH 6/6 (v2)] vfs: rename I_MUTEX_QUOTA now that it's not used for quotas J. Bruce Fields
2012-05-31 20:14 ` J. Bruce Fields
2012-05-31 1:50 ` [PATCH 3/6] vfs: pull ext4's double-i_mutex-locking into common code J. Bruce Fields
2012-05-31 1:50 ` [PATCH 4/6] vfs: don't use PARENT/CHILD lock classes for non-directories J. Bruce Fields
2012-05-31 1:50 ` J. Bruce Fields
2012-05-31 1:50 ` [PATCH 5/6] vfs: take i_mutex on renamed file J. Bruce Fields
2012-05-31 1:50 ` [PATCH 6/6] vfs: rename I_MUTEX_QUOTA now that it's not used for quotas J. Bruce Fields
2012-05-31 1:50 ` J. Bruce Fields
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=1338429016-20119-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.