From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 1/3] gfs2: switch go_xmote_bh glop to pass gh not gl
Date: Tue, 24 Aug 2021 18:12:15 +0200 [thread overview]
Message-ID: <CAHc6FU7SLAyoMc828JPAjb_z9YBM=dESDA3Lir5HWRt0e6ri3Q@mail.gmail.com> (raw)
In-Reply-To: <20210824140241.149386-2-rpeterso@redhat.com>
On Tue, Aug 24, 2021 at 4:02 PM Bob Peterson <rpeterso@redhat.com> wrote:
> Before this patch, the go_xmote_bh function was passed gl, the glock
> pointer. This patch switches it to gh, the holder, which points to the gl.
> This facilitates improvements for the next patch.
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> fs/gfs2/glock.c | 4 ++--
> fs/gfs2/glops.c | 5 +++--
> fs/gfs2/incore.h | 2 +-
> 3 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index e0eaa9cf9fb6..d43eed1696ab 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -562,9 +562,9 @@ static void finish_xmote(struct gfs2_glock *gl, unsigned int ret)
> if (test_and_clear_bit(GLF_DEMOTE_IN_PROGRESS, &gl->gl_flags))
> gfs2_demote_wake(gl);
> if (state != LM_ST_UNLOCKED) {
> - if (glops->go_xmote_bh) {
> + if (gh && glops->go_xmote_bh) {
This changes when the callback is called. Please explain why that's okay.
> spin_unlock(&gl->gl_lockref.lock);
> - rv = glops->go_xmote_bh(gl);
> + rv = glops->go_xmote_bh(gh);
> spin_lock(&gl->gl_lockref.lock);
> if (rv) {
> do_error(gl, rv);
> diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
> index 79c621c7863d..6d0770564493 100644
> --- a/fs/gfs2/glops.c
> +++ b/fs/gfs2/glops.c
> @@ -598,10 +598,11 @@ static int freeze_go_sync(struct gfs2_glock *gl)
>
> /**
> * freeze_go_xmote_bh - After promoting/demoting the freeze glock
> - * @gl: the glock
> + * @gh: the holder of the glock
> */
> -static int freeze_go_xmote_bh(struct gfs2_glock *gl)
> +static int freeze_go_xmote_bh(struct gfs2_holder *gh)
> {
> + struct gfs2_glock *gl = gh->gh_gl;
> struct gfs2_sbd *sdp = gl->gl_name.ln_sbd;
> struct gfs2_inode *ip = GFS2_I(sdp->sd_jdesc->jd_inode);
> struct gfs2_glock *j_gl = ip->i_gl;
> diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
> index 0fe49770166e..354d6230d0f7 100644
> --- a/fs/gfs2/incore.h
> +++ b/fs/gfs2/incore.h
> @@ -217,7 +217,7 @@ struct lm_lockname {
>
> struct gfs2_glock_operations {
> int (*go_sync) (struct gfs2_glock *gl);
> - int (*go_xmote_bh)(struct gfs2_glock *gl);
> + int (*go_xmote_bh)(struct gfs2_holder *gh);
> void (*go_inval) (struct gfs2_glock *gl, int flags);
> int (*go_demote_ok) (const struct gfs2_glock *gl);
> int (*go_lock) (struct gfs2_holder *gh);
> --
> 2.31.1
>
Thanks,
Andreas
next prev parent reply other threads:[~2021-08-24 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 14:02 [Cluster-devel] [GFS2 PATCH 0/3] gfs2: Fix freeze/thaw journal check problems Bob Peterson
2021-08-24 14:02 ` [Cluster-devel] [GFS2 PATCH 1/3] gfs2: switch go_xmote_bh glop to pass gh not gl Bob Peterson
2021-08-24 16:12 ` Andreas Gruenbacher [this message]
2021-08-24 16:48 ` Bob Peterson
2021-08-24 22:27 ` Andreas Gruenbacher
2021-08-25 16:11 ` Bob Peterson
2021-08-24 14:02 ` [Cluster-devel] [GFS2 PATCH 2/3] gfs2: Fix broken freeze_go_xmote_bh Bob Peterson
2021-08-24 16:10 ` Andreas Gruenbacher
2021-08-24 14:02 ` [Cluster-devel] [GFS2 PATCH 3/3] gfs2: Eliminate go_xmote_bh in favor of go_lock Bob Peterson
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='CAHc6FU7SLAyoMc828JPAjb_z9YBM=dESDA3Lir5HWRt0e6ri3Q@mail.gmail.com' \
--to=agruenba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).