linux-ext4 - Re: First stab at ea inode disk format doc updates

lists.openwall.net		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 linux-hardening linux-cve-announce 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:   Thu, 22 Jun 2017 11:52:41 -0700
From:   Tahsin Erdogan <tahsin@...gle.com>
To:     "Darrick J. Wong" <darrick.wong@...cle.com>
Cc:     Andreas Dilger <adilger@...ger.ca>,
        "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: First stab at ea inode disk format doc updates

hi Darrick,

> Also -- what is the value of i_mtime (ea inode parent pointer) when the
> refcount > 1?

In the current implementation, xattr inode format is assumed to be in
the new format (refcount in i_ctime and l_i_version, hash in i_atime).
parent xattr e_hash field incorporates xattr inode hash to achieve
strong binding. If hash validation fails, we fallback to old binding
validation (xattr inode i_mtime == parent ino && xattr inode
i_generation == parent i_generation). The idea is to allow migration
from old lustre disks. So, if refcount is valid then value in i_mtime
is not defined.