On 04/02/18 23:37, Randy Dunlap wrote:
[...]
quoted
+reason, could neither be declared as constant, nor it could take advantage
nor could it
ok
[...]
quoted
+Ex: A policy that is loaded from userspace.
Either
Example:
or
E.g.:
(meaning For example)
ok
[...]
quoted
+Different kernel idrivers and threads can use different pools, for finer
drivers
:-( ok
[...]
quoted
+ in use anymore by the requestor, however it will not become avaiable for
requester; however, available
ok
[...]
quoted
+- pmalloc does not provide locking support wrt allocating vs protecting
Write out "wrt" -> with respect to.
ok
quoted
+ an individual pool, for performance reason. It is recommended to not
reasons. not to
ok & ok
[...]
quoted
+ in the case of using directly vmalloc. The exact number depends on size
of using vmalloc directly. on the size
ok & ok
[...]
quoted
+6. write protect the pool
write-protect
ok
[...]
quoted
+7. use in read-only mode the handlers obtained through the allocations
handles ??
yes
---
thanks, igor
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html