From 6b46b078b701901368bf20a39019949eb4f23106 Mon Sep 17 00:00:00 2001
From: Bryan Drewery <bdrewery@FreeBSD.org>
Date: Thu, 7 May 2015 01:55:39 +0000
Subject: Remove references to Giant in namei(9).  This was removed in r241896.

MFC after:	1 week
Sponsored by:	EMC / Isilon Storage Division
---
 share/man/man9/namei.9 | 18 +-----------------
 1 file changed, 1 insertion(+), 17 deletions(-)

(limited to 'share/man/man9/namei.9')

diff --git a/share/man/man9/namei.9 b/share/man/man9/namei.9
index 0bd827f2cd5e..305665a22c47 100644
--- a/share/man/man9/namei.9
+++ b/share/man/man9/namei.9
@@ -33,14 +33,13 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd March 1, 2012
+.Dd May 6, 2015
 .Dt NAMEI 9
 .Os
 .Sh NAME
 .Nm namei ,
 .Nm NDINIT ,
 .Nm NDFREE ,
-.Nm NDHASGIANT
 .Nd pathname translation and lookup operations
 .Sh SYNOPSIS
 .In sys/param.h
@@ -55,8 +54,6 @@
 .Fc
 .Ft void
 .Fn NDFREE "struct nameidata *ndp" "const uint flags"
-.Ft int
-.Fn NDHASGIANT "struct nameidata *ndp"
 .Sh DESCRIPTION
 The
 .Nm
@@ -73,16 +70,6 @@ or
 depending on whether the
 .Dv LOCKLEAF
 flag was specified or not.
-If the
-.Va Giant
-lock is required,
-.Nm
-will acquire it if the caller indicates it is
-.Dv MPSAFE ,
-in which case the caller must later release
-.Va Giant
-based on the results of
-.Fn NDHASGIANT .
 .Pp
 The
 .Fn NDINIT
@@ -362,6 +349,3 @@ In order to solve this for the cases where both
 and
 .Dv LOCKLEAF
 are used, it is necessary to resort to recursive locking.
-.Pp
-Non-MPSAFE file systems exist, requiring callers to conditionally unlock
-.Va Giant .
-- 
cgit v1.2.3