add caveats section mentioning that kpi routines can result in a call to

VOP_GETATTR() and note this should be considered when using the interface.
also say this limitation is planned on being removed.
This commit is contained in:
elad 2006-07-20 18:47:22 +00:00
parent 5fed711bc8
commit 0553a6cee4

View File

@ -1,4 +1,4 @@
.\" $NetBSD: fileassoc.9,v 1.4 2006/07/16 19:37:55 elad Exp $
.\" $NetBSD: fileassoc.9,v 1.5 2006/07/20 18:47:22 elad Exp $
.\"
.\" Copyright (c) 2006 Elad Efrat <elad@NetBSD.org>
.\" All rights reserved.
@ -28,7 +28,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd July 16, 2006
.Dd July 20, 2006
.Dt FILEASSOC 9
.Os
.Sh NAME
@ -369,3 +369,20 @@ KPI first appeared in
designed and implemented the
.Nm
KPI.
.Sh CAVEATS
The current implementation of
.Nm
uses the file-id as returned from a
.Fn VOP_GETATTR
call to uniquely identify a file inside a mount.
KPI routines that can result in a call to
.Fn VOP_GETATTR
are
.Fn fileassoc_lookup ,
.Fn fileassoc_add ,
.Fn fileassoc_file_delete ,
and
.Fn fileassoc_clear .
This should be taken into consideration when using the interface.
.Pp
This limitation is planned on being removed.