From: 정대호 <daeho.jeong@samsung.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
Nix <nix@esperi.org.uk>, "Theodore Ts'o" <tytso@mit.edu>
Cc: "Linux FS Maling List" <linux-fsdevel@vger.kernel.org>,
정대호 <daeho.jeong@samsung.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Trouble mounting metadata_csum ext4 filesystems with v4.7.x after c9274d891869880648c4ee9365df3ecc7ba2e285: not enough inode bytes checksummed?
Date: Tue, 20 Sep 2016 13:35:58 +0000 [thread overview]
Message-ID: <1153903080.1652319.1474378558082.JavaMail.weblogic@ep1ml103c> (raw)
In-Reply-To: CGME20160920055236epcas1p191f8fd252e18f762fa3ad9704f5e77e2@epcas1p1.samsung.com
[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]
Hi, Sorry to bother you.
> Basically, a 128-byte inode inside a filesystem that allocated 256 bytes
> for each inode. As you point out, the old code would checksum the entire
> allocated space, whether or not the inode core used it. Obviously, you
> want this since inline extended attributes live in that space:
> csum = ext4_chksum(sbi, ei->i_csum_seed, (__u8 *)raw,
> EXT4_INODE_SIZE(inode->i_sb));
> The new code, on the other hand, carefully checksums around the
> i_checksum fields and only bothers to checksum the space between the end
> of i_checksum_hi and the end of the allocated space if the inode core is
> big enough to store i_checksum_hi. Since we allocated 256 bytes for
> each inode, we checksum the first two bytes after byte 128
> (EXT4_GOOD_OLD_INODE_SIZE), but then we see that i_extra_size == 0 so we
> never bother to checksum anything after that. This is of course wrong
> since we no longer checksum the xattr space and we've deviated from the
> pre-4.7.4 (documented) on-disk format.
Oops. I had overlooked the case of that i_extra_size is less than 4.
I misunderstood the previous Darrick's codes calculating inode checksum value.
Sorry about that. :-(
> if (EXT4_INODE_SIZE(inode->i_sb) > EXT4_GOOD_OLD_INODE_SIZE) {
> offset = offsetof(struct ext4_inode, i_checksum_hi);
> csum = ext4_chksum(sbi, csum, (__u8 *)raw +
> EXT4_GOOD_OLD_INODE_SIZE,
> offset - EXT4_GOOD_OLD_INODE_SIZE);
> if (EXT4_FITS_IN_INODE(raw, ei, i_checksum_hi)) {
> csum = ext4_chksum(sbi, csum, (__u8 *)&dummy_csum,
> csum_size);
> offset += csum_size;
> }
> csum = ext4_chksum(sbi, csum, (__u8 *)raw + offset,
> EXT4_INODE_SIZE(inode->i_sb) - offset);
> }
>
> Can you give that a try?
Darrick, your modification looks good enough to me.
Thank you, guys.
prev parent reply other threads:[~2016-09-20 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 14:19 Trouble mounting metadata_csum ext4 filesystems with v4.7.x after c9274d891869880648c4ee9365df3ecc7ba2e285: not enough inode bytes checksummed? Nix
2016-09-20 5:52 ` Darrick J. Wong
2017-01-05 11:09 ` Nick Alcock
2017-01-15 17:34 ` Nick Alcock
[not found] ` <CGME20160920055236epcas1p191f8fd252e18f762fa3ad9704f5e77e2@epcas1p1.samsung.com>
2016-09-20 13:35 ` 정대호 [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=1153903080.1652319.1474378558082.JavaMail.weblogic@ep1ml103c \
--to=daeho.jeong@samsung.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).