[lkml]   [2009]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 04/23] vfs: Introduce infrastructure for revoking a file
Miklos Szeredi <> writes:

> Hi Eric,
> Very interesting work.
> On Mon, 1 Jun 2009, Eric W. Biederman wrote:
>> The file_hotplug_lock has a very unique implementation necessitated by
>> the need to have no performance impact on existing code. Classic locking
>> primitives and reference counting cause pipeline stalls, except for rcu
>> which provides no ability to preventing reading a data structure while
>> it is being updated.
> Well, the simple solution to that is to add another level of indirection:
> old:
> fdtable -> file
> new:
> fdtable -> persistent_file -> file
> Then it is possible to replace persistent_file->file with a revoked
> one under RCU. This has the added advantage that it supports
> arbitrary file replacements, not just ones which return EIO.
> Another advantage is that dereferencing can normally be done "under
> the hood" in fget()/fget_light(). Only code which wants to
> permanently store a file pointer (like the SCM_RIGHTS thing) would
> need to be aware of the extra complexity.
> Would that work, do you think?

Well I went down this path for a little while, and it has some good points.
Unfortunately it appears to be more costly.

fget() and friends are semantically very different my
file_hotplug_read_trylock and unlock. In fact there is very little
overlap. Which means that transparent to the vfs users doesn't
actually work.

We actually have more and less predictable places where we store files.

If there was actually a compelling case for being more general I would
certainly agree that splitting the file structure in two would be a
good deal. As it is that level of flexibility seems to be overkill.


 \ /
  Last update: 2009-06-05 21:09    [W:0.166 / U:1.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site