From mboxrd@z Thu Jan 1 00:00:00 1970 From: igor.stoppa@huawei.com (Igor Stoppa) Date: Fri, 9 Feb 2018 18:41:18 +0200 Subject: [PATCH 6/6] Documentation for Pmalloc In-Reply-To: <29176ee0-f253-ccd7-8201-3f061b5890b0@infradead.org> References: <20180204164732.28241-1-igor.stoppa@huawei.com> <20180204170056.28772-1-igor.stoppa@huawei.com> <20180204170056.28772-2-igor.stoppa@huawei.com> <29176ee0-f253-ccd7-8201-3f061b5890b0@infradead.org> Message-ID: <33d85206-abfb-86cf-d303-b7efba9cc325@huawei.com> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On 04/02/18 23:37, Randy Dunlap wrote: [...] >> +reason, could neither be declared as constant, nor it could take advantage > > nor could it ok [...] >> +Ex: A policy that is loaded from userspace. > > Either > Example: > or > E.g.: > (meaning For example) ok [...] >> +Different kernel idrivers and threads can use different pools, for finer > > drivers :-( ok [...] >> + in use anymore by the requestor, however it will not become avaiable for > > requester; however, available ok [...] >> +- pmalloc does not provide locking support wrt allocating vs protecting > > Write out "wrt" -> with respect to. ok >> + an individual pool, for performance reason. It is recommended to not > > reasons. not to ok & ok [...] >> + in the case of using directly vmalloc. The exact number depends on size > > of using vmalloc directly. on the size ok & ok [...] >> +6. write protect the pool > > write-protect ok [...] >> +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