lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 31 May 2017 12:59:51 -0700
From:   Tahsin Erdogan <>
To:     "Darrick J. Wong" <>
Cc:     Jan Kara <>, "Theodore Ts'o" <>,
        Andreas Dilger <>,
        Dave Kleikamp <>,
        Alexander Viro <>,
        Mark Fasheh <>,
        Joel Becker <>, Jens Axboe <>,
        Deepa Dinamani <>,
        Mike Christie <>,
        Fabian Frederick <>,,,,,,,
        Andreas Dilger <>,
        Kalpak Shah <>,
        James Simmons <>
Subject: Re: [PATCH 01/28] ext4: xattr-in-inode support

>> allowing the ext4/e2fsck to verify the correct inode is accessed.
> Can we store the checksum of the xattr value somewhere?  We already
> checksum the values if they're stored in the ibody or a single external
> block, and I'd hate to lose that protection.
> We could probably reuse one of the inode fields (i_version?) for this.
The crc32c value of the xattr data is currently stored in the xattr inode:

struct ext4_xattr_ea_info {
__le64 ref_count; /* number of xattr entry references */
__le32 hash; /* crc32c hash of xattr data */
__le32 reserved; /* reserved, must be 0 */

We could also save that value in the ext4_xattr_entry->e_value_offs
for stronger binding between parent and xattr inodes. That field is
currently set to 0 for xattr inode references.

Powered by blists - more mailing lists