From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Add missing rcu locking for glock lookup
Date: Thu, 23 Feb 2017 08:08:56 -0500 (EST) [thread overview]
Message-ID: <1549997998.25993663.1487855336135.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <80e1892f-cb02-648f-ec01-58431d9c39a4@redhat.com>
----- Original Message -----
| On 22/02/17 19:19, Bob Peterson wrote:
| > ----- Original Message -----
| > | From: Andrew Price <anprice@redhat.com>
| > |
| > | 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 <agruenba@redhat.com>
| > | ---
| > 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
next prev parent reply other threads:[~2017-02-23 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 15:09 [Cluster-devel] [PATCH] gfs2: Add missing rcu locking for glock lookup Andreas Gruenbacher
2017-02-22 15:13 ` Steven Whitehouse
2017-02-22 15:26 ` Andreas Gruenbacher
2017-02-22 15:28 ` Andreas Gruenbacher
2017-02-22 15:29 ` Steven Whitehouse
2017-02-22 15:34 ` Andreas Gruenbacher
2017-02-22 15:50 ` Steven Whitehouse
2017-02-22 15:18 ` Andrew Price
2017-02-22 19:19 ` Bob Peterson
2017-02-23 10:04 ` Andrew Price
2017-02-23 13:08 ` Bob Peterson [this message]
2017-02-23 14:32 ` Andrew Price
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=1549997998.25993663.1487855336135.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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.