lkml.org 
[lkml]   [2008]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning
From
Date
On Wed, 2008-08-06 at 04:35 +0200, Andi Kleen wrote:
> Eric Paris <eparis@redhat.com> writes:
>
> > 5. Fine-grained caching
> > -----------------------
> > It is necessary to select which filesystems can be safely cached and
> > which must not be. For example it is not a good idea to allow caching of
> > network filesystems because their content can be changed invisibly. Disk
> > based and some virtual filesystems can be cached safely on the other
> > hand.
>
> Actually local disk file systems can be changed invisibly to the VFS too by
> directly writing to the block device. This does not change the
> page cache, but the on disk copy and when a page is pruned from
> RAM and reloaded VFS will see the new contents without knowing
> about any change. How would you stop that in your
> proposal? I assume you could always require a special LKM that
> forbids block writes for anything mounted, but that has other problems
> too and one wuld need to be extremly careful of holes in
> such a protection scheme (e.g. overlapping partitions)

I didn't consider it. Most likely at the end of the day the finding
will be, "if you can write directly to the block device you already won
since there as so many other things you can do to subvert the system."

Admittedly its the first technical point brought up on list that I
didn't consider at all (lots of other things brought up on list that
need more thought that weren't exactly technical details, don't let me
seem like I'm downplaying those)

-Eric



\
 
 \ /
  Last update: 2008-08-06 05:47    [from the cache]
©2003-2011 Jasper Spaans