linux-kernel - Re: [PATCH] writeback: guard against jiffies wraparound on inode->dirtied

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, 2 Apr 2009 00:12:24 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jeff Layton <jlayton@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	fengguang.wu@...el.com
Subject: Re: [PATCH] writeback: guard against jiffies wraparound on inode->dirtied_when checks (try #3)

On Wed, Apr 01, 2009 at 05:26:30PM -0400, Jeff Layton wrote:
> One possibility might be a new debugging option. We could add
> replacement time_after() and time_before() macros that also check
> whether the difference in times is beyond a certain threshold
> (maybe a day or week or so), and pop a printk or otherwise record
> info about it when one is detected?

Makes sense. However it might be hard to get people to run kernels
with heavy debugging options for that long.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/