From: "Darrick J. Wong" <djwong@kernel.org>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeroen van Wolffelaar <jeroen@wolffelaar.nl>
Subject: Re: [PATCH v2] ext4: set csum seed in tmp inode while migrating to extents
Date: Tue, 14 Dec 2021 16:49:45 -0800 [thread overview]
Message-ID: <20211215004945.GD69182@magnolia> (raw)
In-Reply-To: <20211214175058.19511-1-lhenriques@suse.de>
On Tue, Dec 14, 2021 at 05:50:58PM +0000, Luís Henriques wrote:
> When migrating to extents, the temporary inode will have it's own checksum
> seed. This means that, when swapping the inodes data, the inode checksums
> will be incorrect.
>
> This can be fixed by recalculating the extents checksums again. Or simply
> by copying the seed into the temporary inode.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=213357
> Reported-by: Jeroen van Wolffelaar <jeroen@wolffelaar.nl>
> Signed-off-by: Luís Henriques <lhenriques@suse.de>
> ---
> fs/ext4/migrate.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> changes since v1:
>
> * Dropped tmp_ei variable
> * ->i_csum_seed is now initialised immediately after tmp_inode is created
> * New comment about the seed initialization and stating that recovery
> needs to be fixed.
>
> Cheers,
> --
> Luís
>
> diff --git a/fs/ext4/migrate.c b/fs/ext4/migrate.c
> index 7e0b4f81c6c0..36dfc88ce05b 100644
> --- a/fs/ext4/migrate.c
> +++ b/fs/ext4/migrate.c
> @@ -459,6 +459,17 @@ int ext4_ext_migrate(struct inode *inode)
> ext4_journal_stop(handle);
> goto out_unlock;
> }
> + /*
> + * Use the correct seed for checksum (i.e. the seed from 'inode'). This
> + * is so that the metadata blocks will have the correct checksum after
> + * the migration.
> + *
> + * Note however that, if a crash occurs during the migration process,
> + * the recovery process is broken because the tmp_inode checksums will
> + * be wrong and the orphans cleanup will fail.
...and then what does the user do?
--D
> + */
> + ei = EXT4_I(inode);
> + EXT4_I(tmp_inode)->i_csum_seed = ei->i_csum_seed;
> i_size_write(tmp_inode, i_size_read(inode));
> /*
> * Set the i_nlink to zero so it will be deleted later
> @@ -502,7 +513,6 @@ int ext4_ext_migrate(struct inode *inode)
> goto out_tmp_inode;
> }
>
> - ei = EXT4_I(inode);
> i_data = ei->i_data;
> memset(&lb, 0, sizeof(lb));
>
next prev parent reply other threads:[~2021-12-15 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 17:50 [PATCH v2] ext4: set csum seed in tmp inode while migrating to extents Luís Henriques
2021-12-15 0:49 ` Darrick J. Wong [this message]
2021-12-15 10:46 ` Luís Henriques
2021-12-15 11:28 ` Jan Kara
2021-12-15 14:12 ` Lukas Czerner
2021-12-15 15:37 ` Luís Henriques
2021-12-16 11:23 ` Luís Henriques
2021-12-16 18:32 ` Theodore Ts'o
2021-12-17 9:35 ` Lukas Czerner
2021-12-28 22:40 ` Pavel Machek
2021-12-30 6:56 ` Theodore Ts'o
2021-12-17 15:09 ` Jeroen van Wolffelaar
2022-01-06 4:41 ` Theodore Ts'o
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=20211215004945.GD69182@magnolia \
--to=djwong@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=jeroen@wolffelaar.nl \
--cc=lhenriques@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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