Messages in this thread | | | Subject | Re: PATCH [2/7] Fix posix locking code | From | Trond Myklebust <> | Date | Sat, 14 Aug 2004 16:18:31 -0400 |
| |
På lau , 14/08/2004 klokka 16:00, skreiv Matthew Wilcox:
> I know I said I thought file_lock_operations was the right thing to > do ... but now I think that this isn't a property of the file_lock so > much as it is a property of the underlying filesystem. I think putting a > lock_operations into struct file is maybe a bit much. How about adding > a lock_operations pointer to file_operations?
Lock operations are as much a property of the lock *type*. A BSD lock may/will have an entirely different set of callbacks.
Trond - 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/
| |