linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Ye Bin <yebin10@huawei.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	jack@suse.cz
Subject: Re: [PATCH -next v2 1/6] ext4: init seq with random value in kmmpd
Date: Thu, 7 Oct 2021 14:26:04 +0200	[thread overview]
Message-ID: <20211007122604.GF12712@quack2.suse.cz> (raw)
In-Reply-To: <20210911090059.1876456-2-yebin10@huawei.com>

On Sat 11-09-21 17:00:54, Ye Bin wrote:
> If two host has the same nodename, and seq start from 0, May cause the
> detection mechanism to fail.
> So init seq with random value to accelerate conflict detection.
> 
> Signed-off-by: Ye Bin <yebin10@huawei.com>

Thanks for the patch. I agree the code in kmmpd looks suspicious.  The
sequence number is initialized to a random number in
ext4_multi_mount_protect() which is called before kmmpd is started. I think
kmmpd() should initialize its 'seq' to a number fetched from the mmp
block, instead of 0 as is currently in the code. I don't think generating a
new random number as you do is really needed...

								Honza

> ---
>  fs/ext4/mmp.c | 32 ++++++++++++++++----------------
>  1 file changed, 16 insertions(+), 16 deletions(-)
> 
> diff --git a/fs/ext4/mmp.c b/fs/ext4/mmp.c
> index cebea4270817..12af6dc8457b 100644
> --- a/fs/ext4/mmp.c
> +++ b/fs/ext4/mmp.c
> @@ -122,6 +122,21 @@ void __dump_mmp_msg(struct super_block *sb, struct mmp_struct *mmp,
>  		       (int)sizeof(mmp->mmp_bdevname), mmp->mmp_bdevname);
>  }
>  
> +/*
> + * Get a random new sequence number but make sure it is not greater than
> + * EXT4_MMP_SEQ_MAX.
> + */
> +static unsigned int mmp_new_seq(void)
> +{
> +	u32 new_seq;
> +
> +	do {
> +		new_seq = prandom_u32();
> +	} while (new_seq > EXT4_MMP_SEQ_MAX);
> +
> +	return new_seq;
> +}
> +
>  /*
>   * kmmpd will update the MMP sequence every s_mmp_update_interval seconds
>   */
> @@ -132,7 +147,7 @@ static int kmmpd(void *data)
>  	struct buffer_head *bh = EXT4_SB(sb)->s_mmp_bh;
>  	struct mmp_struct *mmp;
>  	ext4_fsblk_t mmp_block;
> -	u32 seq = 0;
> +	u32 seq = mmp_new_seq();
>  	unsigned long failed_writes = 0;
>  	int mmp_update_interval = le16_to_cpu(es->s_mmp_update_interval);
>  	unsigned mmp_check_interval;
> @@ -258,21 +273,6 @@ void ext4_stop_mmpd(struct ext4_sb_info *sbi)
>  	}
>  }
>  
> -/*
> - * Get a random new sequence number but make sure it is not greater than
> - * EXT4_MMP_SEQ_MAX.
> - */
> -static unsigned int mmp_new_seq(void)
> -{
> -	u32 new_seq;
> -
> -	do {
> -		new_seq = prandom_u32();
> -	} while (new_seq > EXT4_MMP_SEQ_MAX);
> -
> -	return new_seq;
> -}
> -
>  /*
>   * Protect the filesystem from being mounted more than once.
>   */
> -- 
> 2.31.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2021-10-07 12:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11  9:00 [PATCH -next v2 0/6] Fix some issues about mmp Ye Bin
2021-09-11  9:00 ` [PATCH -next v2 1/6] ext4: init seq with random value in kmmpd Ye Bin
2021-10-07 12:26   ` Jan Kara [this message]
2021-10-08  1:50     ` yebin
2021-09-11  9:00 ` [PATCH -next v2 2/6] ext4: introduce last_check_time record previous check time Ye Bin
2021-10-07 12:31   ` Jan Kara
2021-10-08  1:56     ` yebin
2021-10-08  2:38       ` yebin
2021-10-12  8:47         ` Jan Kara
2021-10-12 11:46           ` yebin
2021-10-13  9:38             ` Jan Kara
2021-10-13 12:33               ` yebin
2021-10-13 21:41               ` Theodore Ts'o
2021-10-15  3:21                 ` Andreas Dilger
2021-10-15  3:21                 ` Andreas Dilger
2021-09-11  9:00 ` [PATCH -next v2 3/6] ext4: compare to local seq and nodename when check conflict Ye Bin
2021-10-07 12:36   ` Jan Kara
2021-09-11  9:00 ` [PATCH -next v2 4/6] ext4: avoid to re-read mmp check data get from page cache Ye Bin
2021-10-07 12:44   ` Jan Kara
2021-10-08  3:52     ` yebin
2021-09-11  9:00 ` [PATCH -next v2 5/6] ext4: avoid to double free s_mmp_bh Ye Bin
2021-09-11  9:00 ` [PATCH -next v2 6/6] ext4: fix possible store wrong check interval value in disk when umount Ye Bin
2021-10-07 13:12   ` Jan Kara
2021-10-08  3:49     ` yebin

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=20211007122604.GF12712@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yebin10@huawei.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).