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 4/6] ext4: avoid to re-read mmp check data get from page cache
Date: Thu, 7 Oct 2021 14:44:22 +0200 [thread overview]
Message-ID: <20211007124422.GI12712@quack2.suse.cz> (raw)
In-Reply-To: <20210911090059.1876456-5-yebin10@huawei.com>
On Sat 11-09-21 17:00:57, Ye Bin wrote:
> As call read_mmp_block pass bh_check which value is NULL, then call
> sb_getblk to get buffer_head. But mmp_block's buffer_head is already exist
> which also is uptodate. Lead to compare the same data.
>
> Signed-off-by: Ye Bin <yebin10@huawei.com>
This looks good, except that read_mmp_block() also releases bh it is passed
in case of error. So it can free buffer head which is still referenced from
EXT4_SB(sb)->s_mmp_bh and cause use-after-free issues.
I guess I would just get rid of sb_getblk() in read_mmp_block() and always
expect valid bh passed. The only place that passes NULL bh after this
patch is one case in ext4_multi_mount_protect() and that can call
sb_getblk() on its own. That way we can also simplify read_mmp_block()
prototype to:
static int read_mmp_block(struct super_block *sb, struct buffer_head *bh);
Honza
> ---
> fs/ext4/mmp.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/fs/ext4/mmp.c b/fs/ext4/mmp.c
> index 4433fe7e9e86..007bde3c12b8 100644
> --- a/fs/ext4/mmp.c
> +++ b/fs/ext4/mmp.c
> @@ -213,10 +213,7 @@ static int kmmpd(void *data)
> * we need to check if the MMP block is as we write it.
> */
> if (jiffies - last_check_time > mmp_check_interval * HZ) {
> - struct buffer_head *bh_check = NULL;
> - struct mmp_struct *mmp_check;
> -
> - retval = read_mmp_block(sb, &bh_check, mmp_block);
> + retval = read_mmp_block(sb, &bh, mmp_block);
> if (retval) {
> ext4_error_err(sb, -retval,
> "error reading MMP data: %d",
> @@ -224,20 +221,18 @@ static int kmmpd(void *data)
> goto wait_to_exit;
> }
>
> - mmp_check = (struct mmp_struct *)(bh_check->b_data);
> - if (seq != mmp_check->mmp_seq ||
> - memcmp(nodename, mmp_check->mmp_nodename,
> - sizeof(mmp->mmp_nodename))) {
> - dump_mmp_msg(sb, mmp_check,
> + mmp = (struct mmp_struct *)(bh->b_data);
> + if (seq != le32_to_cpu(mmp->mmp_seq) ||
> + memcmp(nodename, mmp->mmp_nodename,
> + sizeof(nodename))) {
> + dump_mmp_msg(sb, mmp,
> "Error while updating MMP info. "
> "The filesystem seems to have been"
> " multiply mounted.");
> ext4_error_err(sb, EBUSY, "abort");
> - put_bh(bh_check);
> retval = -EBUSY;
> goto wait_to_exit;
> }
> - put_bh(bh_check);
> last_check_time = jiffies;
> }
>
> --
> 2.31.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-10-07 12:44 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
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 [this message]
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=20211007124422.GI12712@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).