Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Fix recovery slot bumping
Date: Mon, 26 Aug 2019 15:58:02 -0400 (EDT)	[thread overview]
Message-ID: <1711812526.10714872.1566849482829.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190826161444.10573-1-agruenba@redhat.com>

----- Original Message -----
> Get rid of the assumption that the number of slots can at most increase by
> RECOVER_SIZE_INC (16) in set_recover_size.
> 
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> ---
>  fs/gfs2/lock_dlm.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c
> index 4361804646d8..2bc7a334aa0a 100644
> --- a/fs/gfs2/lock_dlm.c
> +++ b/fs/gfs2/lock_dlm.c
> @@ -1035,12 +1035,12 @@ static int set_recover_size(struct gfs2_sbd *sdp,
> struct dlm_slot *slots,
>  	}
>  
>  	old_size = ls->ls_recover_size;
> -
> -	if (old_size >= max_jid + 1)
> +	new_size = old_size;
> +	while (new_size < max_jid + 1)
> +		new_size += RECOVER_SIZE_INC;
> +	if (old_size == new_size)
>  		return 0;
>  
> -	new_size = old_size + RECOVER_SIZE_INC;
> -
>  	submit = kcalloc(new_size, sizeof(uint32_t), GFP_NOFS);
>  	result = kcalloc(new_size, sizeof(uint32_t), GFP_NOFS);
>  	if (!submit || !result) {
> --
> 2.20.1

Yes, that works, although I think it's more clear to say:
+	if (new_size == old_size)
than:
+	if (old_size == new_size)
IOW, it just sounds better. But whatever. It works either way.

Bob



      reply	other threads:[~2019-08-26 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 16:14 [Cluster-devel] [PATCH] gfs2: Fix recovery slot bumping Andreas Gruenbacher
2019-08-26 19:58 ` Bob Peterson [this message]

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=1711812526.10714872.1566849482829.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox