From: Andrew W Elble Date: Tue, 06 Oct 2015 14:40:01 -0400 Subject: [Cluster-devel] [GFS2 PATCH 06/15] GFS2: Prevent gl_delete work for re-used inodes In-Reply-To: <1444059397-4705-7-git-send-email-rpeterso@redhat.com> (Bob Peterson's message of "Mon, 5 Oct 2015 10:36:28 -0500") References: <1444059397-4705-1-git-send-email-rpeterso@redhat.com> <1444059397-4705-7-git-send-email-rpeterso@redhat.com> Message-ID: List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Bob Peterson writes: > This patch adds a new glock flag GLF_INODE_DELETING which signifies > when a glock is being used to change an inode from unlinked to > deleted. The flag is used in a few places: This is the change I made to what we're testing: diff --git a/fs/gfs2/trace_gfs2.h b/fs/gfs2/trace_gfs2.h index 20c007d..80f2ee7 100644 --- a/fs/gfs2/trace_gfs2.h +++ b/fs/gfs2/trace_gfs2.h @@ -57,7 +57,8 @@ {(1UL << GLF_QUEUED), "q" }, \ {(1UL << GLF_LRU), "L" }, \ {(1UL << GLF_OBJECT), "o" }, \ - {(1UL << GLF_BLOCKING), "b" }) + {(1UL << GLF_BLOCKING), "b" }, \ + {(1UL << GLF_INODE_DELETING), "-" }) #ifndef NUMPTY #define NUMPTY -- Andrew W. Elble aweits@discipline.rit.edu Infrastructure Engineer, Communications Technical Lead Rochester Institute of Technology PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912