From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Peterson Date: Mon, 27 Jun 2016 11:21:25 -0400 (EDT) Subject: [Cluster-devel] [PATCH v2] gfs2: Lock holder cleanup In-Reply-To: <1466164999-31196-1-git-send-email-agruenba@redhat.com> References: <1466012373-32507-1-git-send-email-agruenba@redhat.com> <1466164999-31196-1-git-send-email-agruenba@redhat.com> Message-ID: <273663754.3146438.1467040885344.JavaMail.zimbra@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ----- Original Message ----- | Make the code more readable by cleaning up the different ways of | initializing lock holders and checking for initialized lock holders: | mark lock holders as uninitialized by setting the holder's glock to NULL | (gfs2_holder_mark_uninitialized) instead of zeroing out the entire | object or using a separate flag. Recognize initialized holders by their | non-NULL glock (gfs2_holder_initialized). Don't zero out holder objects | which are immeditiately initialized via gfs2_holder_init or | gfs2_glock_nq_init. | | Signed-off-by: Andreas Gruenbacher | --- Hi, Thanks. This is now applied to the for-next branch of the linux-gfs2 tree: https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs?h=for-next&id=6df9f9a253c7dc9f8ed18bf89d762de350a31813 Regards, Bob Peterson Red Hat File Systems