add a comment to note that a process's vmspace may change, but so far
only aiod does this and is also marked P_SYSTEM, the locations that reference p->p_vmspace usually do it within the context of the caller, the async access from the vm system is protected by the fact that it will skip over P_SYSTEM processes. Ok'd by: jhb
This commit is contained in:
parent
df8f79b9de
commit
f1556a21a4
@ -126,7 +126,9 @@ struct pargs {
|
||||
* associated comment.
|
||||
* * - not yet protected
|
||||
* a - only touched by curproc or parent during fork/wait
|
||||
* b - created at fork, never chagnes
|
||||
* b - created at fork, never changes
|
||||
* (exception aiods switch vmspaces, but they are also
|
||||
* marked 'P_SYSTEM' so hopefully it will be left alone)
|
||||
* c - locked by proc mtx
|
||||
* d - locked by allproc_lock lock
|
||||
* e - locked by proctree_lock lock
|
||||
|
Loading…
Reference in New Issue
Block a user