Re: [PATCH][2.1.71] BSD revoke() syscall

[Alan Cox]

> Good point but how, then, do I deal correctly with close()?  I'm not
> allowed to modify *(filp->f_op) (would break the whole filesystem,
> wouldn't it?), but I _am_ allowed to change filp->f_op, if I'm not
> mistaken.  Except that then it's not possible cleanly to handle the
> file close.

How about kmallocing a new f_op set with an attached private pointer to the
original one, so your close flips it back and frees the temporary one ?

> I had wondered about these -- what's the policy?  I thought "I've started
> so I'll finish" was the rule :)

No idea