Re: [PATCH] cowlinks v2

[Jörn Engel]

On Sat, 20 March 2004 10:03:05 -0500, Patrick J. LoPresti wrote:
> 
> What happens if the disk fills while you are making the copy?  Will
> open(2) on an *existing file* then return ENOSPC?

Correct.  It would be possible to always succeed and return -ENOSPC
on every write().  But then mmap() has the same problem again, so
serious headache would be the only gain from this little excercise.

> I do not think you can implement this without changing the interface
> to open(2).  Which means applications have to be made aware of it
> anyway.  Which means you might as well leave your implementation as-is
> and let userspace worry about creating the copy (and dealing with the
> resulting errors).

Good point.  Vote is now 2:0 for the simple approach.

Jörn

-- 
"Translations are and will always be problematic. They inflict violence 
upon two languages." (translation from German)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/