linux-ext4 - Re: [PATCH 3/4] vfs: don't let the dirty time inodes get more than a day stale

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: <656297ED-3A8F-4437-8356-950F8C77D9DE@dilger.ca>
Date:	Fri, 21 Nov 2014 17:09:49 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Theodore Ts'o <tytso@....edu>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 3/4] vfs: don't let the dirty time inodes get more than a day stale

On Nov 21, 2014, at 3:36 PM, Theodore Ts'o <tytso@....edu> wrote:
>> and "days_since_boot" should be declared unsigned short so it wraps
>> in the same way as i_ts_dirty_day
> 
> Good point, thanks.  This will only be an issue after the system has
> been up for almost 90 years, but we might as well get it right,

Speaking of stuff in the future, it looks like the patch to fix the
ext4 dates-beyond-epoch handling hasn't landed yet?

The last email I found related to that is in "[PATCH] fs: ext4: Sign-extend tv_sec after ORing in epoch bits", but the patch that I actually thought was ready to land was "[PATCH v8 1/2] ext4: Fix handling of extended tv_sec (bug 23732)" and the matching e2fsprogs patch:

http://lkml.org/lkml/2014/2/13/667
http://lkml.org/lkml/2014/2/13/670

Would be nice to get them landed, since we have less than 20 years
left, and at some point there will be embedded systems or VMs using
ext4 that may live long enough to hit the bug...

Cheers, Andreas

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)