From: Andi Kleen <andi@firstfloor.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: [PATCH] writeback: guard against jiffies wraparound on inode->dirtied_when checks (try #3)
Date: Thu, 2 Apr 2009 00:12:24 +0200 [thread overview]
Message-ID: <20090401221224.GW11935@one.firstfloor.org> (raw)
In-Reply-To: <20090401172630.31c6ac7c@tleilax.poochiereds.net>
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@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-01 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 17:37 [PATCH] writeback: guard against jiffies wraparound on inode->dirtied_when checks (try #3) Jeff Layton
2009-04-01 20:22 ` Andi Kleen
2009-04-01 21:26 ` Jeff Layton
2009-04-01 22:12 ` Andi Kleen [this message]
2009-04-02 11:58 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090401221224.GW11935@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox