[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703161637001.26209@sbz-30.cs.Helsinki.FI>
Date: Fri, 16 Mar 2007 16:45:39 +0200 (EET)
From: Pekka J Enberg <penberg@...helsinki.fi>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: linux-kernel@...r.kernel.org, hch@...radead.org,
alan@...rguk.ukuu.org.uk
Subject: Re: [PATCH 2/5] revoke: core code
On Fri, 16 Mar 2007, Andrew Morton wrote:
> What you're trying to do here is very similar to truncate(), and truncate()
> has had a lot of work put into it, and it does work.
Indeed. revoke() is the same as truncate() without, well, the truncation
part.
On Fri, 16 Mar 2007, Andrew Morton wrote:
> However, modifying i_size like this might be a problem - the inode could be
> dirty and it'll get written to disk! Perhaps we could change i_size_read()
> to cheat and to return zero if there's a revoke in progress.
Hmph, it's probably going to get too painful so I'll look at adding some
hooks to do_generic_mapping_read()...
Pekka
-
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/
Powered by blists - more mailing lists