Re: [PATCH] new syscall: flink

Werner Almesberger (wa@almesberger.net)
Mon, 7 Apr 2003 15:43:03 -0300


Clayton Weaver wrote:
> If the client process subsequently flink()s to the inode, it is merely
> a zerocopy file copy.

As far as access to the data is concerned, yes. But there's also the
location of the file. E.g. this might enable you to fill somebody
else's quota, or, if distinct physical devices can be be covered by
the same file system, to access a physical device that would
otherwise not be available to you.

Example: I write some kind of RAID mounted at /world, that contains
my disk under /world/disk, and some Flash storage under /world/flash.
I protect /world/flash against writes by other people. If a
read-only FD could be turned into something writeable, some malicious
creature could "wear out" my Flash by writing to it a lot of times.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/