All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Yunlei He <heyunlei@hihonor.com>
Cc: chao@kernel.org, jaegeuk@kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-fscrypt@vger.kernel.org, bintian.wang@hihonor.com,
	stable@vger.kernel.org
Subject: Re: [f2fs-dev][PATCH] f2fs: fsverity: modify truncation for verity enable failed
Date: Tue, 2 Mar 2021 12:09:58 -0800	[thread overview]
Message-ID: <YD6bltna2vBFVlgV@sol.localdomain> (raw)
In-Reply-To: <20210302113850.17011-1-heyunlei@hihonor.com>

Hi Yunlei,

On Tue, Mar 02, 2021 at 07:38:50PM +0800, Yunlei He wrote:
> If file enable verity failed, should truncate anything wrote
> past i_size, including cache pages. Move the truncation to
> the end of function, in case of f2fs set xattr failed.
> 
> Fixes: 95ae251fe828 ("f2fs: add fs-verity support")
> Cc: <stable@vger.kernel.org> # v5.4+
> Signed-off-by: Yunlei He <heyunlei@hihonor.com>
> ---
>  fs/f2fs/verity.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/f2fs/verity.c b/fs/f2fs/verity.c
> index 054ec852b5ea..610f2a9b4928 100644
> --- a/fs/f2fs/verity.c
> +++ b/fs/f2fs/verity.c
> @@ -169,10 +169,6 @@ static int f2fs_end_enable_verity(struct file *filp, const void *desc,
>  			err = filemap_write_and_wait(inode->i_mapping);
>  	}
>  
> -	/* If we failed, truncate anything we wrote past i_size. */
> -	if (desc == NULL || err)
> -		f2fs_truncate(inode);
> -
>  	clear_inode_flag(inode, FI_VERITY_IN_PROGRESS);
>  
>  	if (desc != NULL && !err) {
> @@ -185,6 +181,13 @@ static int f2fs_end_enable_verity(struct file *filp, const void *desc,
>  			f2fs_mark_inode_dirty_sync(inode, true);
>  		}
>  	}
> +
> +	/* If we failed, truncate anything we wrote past i_size. */
> +	if (desc == NULL || err) {
> +		truncate_inode_pages(inode->i_mapping, inode->i_size);
> +		f2fs_truncate(inode);
> +	}
> +
>  	return err;

This is better, but we really should properly separate the success path from the
error paths in this function; otherwise it's too hard to understand.  Also, the
same bugs need to be fixed in ext4 too, and the commit message could be better.
I went ahead and sent out a new patchset which addresses all this
(https://lkml.kernel.org/linux-f2fs-devel/20210302200420.137977-1-ebiggers@kernel.org/T/#u);
can you take a look at that instead?  Thanks!

- Eric

WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Yunlei He <heyunlei@hihonor.com>
Cc: stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-fscrypt@vger.kernel.org, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fsverity: modify truncation for verity enable failed
Date: Tue, 2 Mar 2021 12:09:58 -0800	[thread overview]
Message-ID: <YD6bltna2vBFVlgV@sol.localdomain> (raw)
In-Reply-To: <20210302113850.17011-1-heyunlei@hihonor.com>

Hi Yunlei,

On Tue, Mar 02, 2021 at 07:38:50PM +0800, Yunlei He wrote:
> If file enable verity failed, should truncate anything wrote
> past i_size, including cache pages. Move the truncation to
> the end of function, in case of f2fs set xattr failed.
> 
> Fixes: 95ae251fe828 ("f2fs: add fs-verity support")
> Cc: <stable@vger.kernel.org> # v5.4+
> Signed-off-by: Yunlei He <heyunlei@hihonor.com>
> ---
>  fs/f2fs/verity.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/f2fs/verity.c b/fs/f2fs/verity.c
> index 054ec852b5ea..610f2a9b4928 100644
> --- a/fs/f2fs/verity.c
> +++ b/fs/f2fs/verity.c
> @@ -169,10 +169,6 @@ static int f2fs_end_enable_verity(struct file *filp, const void *desc,
>  			err = filemap_write_and_wait(inode->i_mapping);
>  	}
>  
> -	/* If we failed, truncate anything we wrote past i_size. */
> -	if (desc == NULL || err)
> -		f2fs_truncate(inode);
> -
>  	clear_inode_flag(inode, FI_VERITY_IN_PROGRESS);
>  
>  	if (desc != NULL && !err) {
> @@ -185,6 +181,13 @@ static int f2fs_end_enable_verity(struct file *filp, const void *desc,
>  			f2fs_mark_inode_dirty_sync(inode, true);
>  		}
>  	}
> +
> +	/* If we failed, truncate anything we wrote past i_size. */
> +	if (desc == NULL || err) {
> +		truncate_inode_pages(inode->i_mapping, inode->i_size);
> +		f2fs_truncate(inode);
> +	}
> +
>  	return err;

This is better, but we really should properly separate the success path from the
error paths in this function; otherwise it's too hard to understand.  Also, the
same bugs need to be fixed in ext4 too, and the commit message could be better.
I went ahead and sent out a new patchset which addresses all this
(https://lkml.kernel.org/linux-f2fs-devel/20210302200420.137977-1-ebiggers@kernel.org/T/#u);
can you take a look at that instead?  Thanks!

- Eric


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-03-03  4:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 11:38 [f2fs-dev][PATCH] f2fs: fsverity: modify truncation for verity enable failed Yunlei He
2021-03-02 11:38 ` [f2fs-dev] [PATCH] " Yunlei He
2021-03-02 20:09 ` Eric Biggers [this message]
2021-03-02 20:09   ` Eric Biggers

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=YD6bltna2vBFVlgV@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=bintian.wang@hihonor.com \
    --cc=chao@kernel.org \
    --cc=heyunlei@hihonor.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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.