Author: ion
Date: Thu May 25 00:29:02 2006
New Revision: 22018
URL: http://svn.reactos.ru/svn/reactos?rev=22018&view=rev
Log:
[AUDIT] namespc.c: The namespace functions are publically document and wrap around a ROS-internal ObFindObject function which is very different from the way NT handles parsing. The capture of attribute information was based off a public structure, and the function used does not seem to exist in NT (based on a google search). Object Manager Initialization is internal to ROS and performs generic/trivial intialization tasks, which seem to match the description present in Windows Internals as well as Windows NT File System Internals. Finally, Object Type creation is a ROS-internal function based off documentation found in Gl00my's object manager article as well as local debugging done with WinDBG which helped define the purpose of DefaultObject.
Modified:
trunk/reactos/ntoskrnl/ob/namespc.c (props changed)
Propchange: trunk/reactos/ntoskrnl/ob/namespc.c
------------------------------------------------------------------------------
--- svn:needs-lock (original)
+++ svn:needs-lock (removed)
@@ -1,1 +1,0 @@
-*
Author: ion
Date: Thu May 25 00:16:09 2006
New Revision: 22017
URL: http://svn.reactos.ru/svn/reactos?rev=22017&view=rev
Log:
[AUDIT] security.c: All these functions are simply wrappers around the SecurityProcedure callback, which actually does all the work (and is located in /se). Their implementation is trivial and could not have been done another way (it may likely differ from the 100% NT implementation (which I am not aware of), but the current implementation seems obvious to me and I don't see anything missing.
Modified:
trunk/reactos/ntoskrnl/ob/security.c (props changed)
Propchange: trunk/reactos/ntoskrnl/ob/security.c
------------------------------------------------------------------------------
--- svn:needs-lock (original)
+++ svn:needs-lock (removed)
@@ -1,1 +1,0 @@
-*