From: Bob Peterson Date: Thu, 23 Feb 2017 08:08:56 -0500 (EST) Subject: [Cluster-devel] [PATCH] gfs2: Add missing rcu locking for glock lookup In-Reply-To: <80e1892f-cb02-648f-ec01-58431d9c39a4@redhat.com> References: <1487776193-18506-1-git-send-email-agruenba@redhat.com> <997067545.25761689.1487791150131.JavaMail.zimbra@redhat.com> <80e1892f-cb02-648f-ec01-58431d9c39a4@redhat.com> Message-ID: <1549997998.25993663.1487855336135.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 ----- | On 22/02/17 19:19, Bob Peterson wrote: | > ----- Original Message ----- | > | From: Andrew Price | > | | > | We must hold the rcu read lock across looking up glocks and trying to | > | bump their refcount to prevent the glocks from being freed in between. | > | | > | 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/?h=for-next&id=329414f6696541d1680f5867ce747050b8054e66 | | I think Andreas intended for me to be the "author" of this commit, which | is what git am should have done with the "From:" line. Not that I'm | overly bothered about it :) | | Andy | Sorry about that. I fixed it now. Regards, Bob Peterson Red Hat File Systems