From 23e62e7654347c8fe8f01c1e99511a6337340d55 Mon Sep 17 00:00:00 2001
From: Edward Tomasz Napierala <trasz@FreeBSD.org>
Date: Wed, 11 Nov 2009 13:49:22 +0000
Subject: [PATCH] Revert r198873.  Having different VAPPEND semantics for
 VOP_ACCESS(9) and VOP_ACCESSX(9) is not a good idea.

---
 sys/kern/vfs_default.c | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/sys/kern/vfs_default.c b/sys/kern/vfs_default.c
index d37e0662f266..b80d03d0e9ec 100644
--- a/sys/kern/vfs_default.c
+++ b/sys/kern/vfs_default.c
@@ -353,14 +353,6 @@ vop_stdaccessx(struct vop_accessx_args *ap)
 	if (accmode == 0)
 		return (0);
 
-	/*
-	 * Many VOP_APPEND implementations don't expect VAPPEND without VWRITE
-	 * being set, e.g. they check whether the filesystem is read-only only
-	 * when VWRITE is set.  Make sure we don't confuse them.
-	 */
-	if (accmode & VAPPEND)
-		accmode |= VWRITE;
-
 	return (VOP_ACCESS(ap->a_vp, accmode, ap->a_cred, ap->a_td));
 }