linux-ext4 - Re: rfc: [patch] change attribute for ext3

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]

Message-ID: <20060915161816.GG6441@schatzie.adilger.int>
Date:	Fri, 15 Sep 2006 10:18:16 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Alexandre Ratchov <alexandre.ratchov@...l.net>
Cc:	linux-ext4@...r.kernel.org, nfsv4@...ux-nfs.org
Subject: Re: rfc: [patch] change attribute for ext3

On Sep 15, 2006  12:19 +0200, Alexandre Ratchov wrote:
> BTW, note that when we'll add support for nanosecond time-stamps, we still
> have the same problem, because with a very high clock and time-stamp
> resolutions, we'll have to update the inode on every change.

If we have a journal commit callback, then even if the in-core inode ctime
is changed continually, the on-disk inode will be updated exactly once per
jbd transaction.  The problem as it stands now is that the ext3/VFS code
doesn't know where a transaction boundary is, so it has to continually
update the on-disk inode to make sure that the changes are in the relevant
transaction.

I recall a long time ago that Andrew got significant improvement from
reducing the number of mark_inode_dirty() calls in ext3, just because of
avoiding the repeated core->disk inode packing.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html