06.09.25 01:01, Daniel P. Smith:
Hi Sergiy,
If you don't mind, please CC me directly, as I am the only XSM
maintainer for which you will need my Ack. And for whatever reason, I
cannot find the v2 post in my xen-devel folder. If you want to resend me
v2, it would be greatly appreciated.
ye
On 26.09.2025 08:32, Sergiy Kibrik wrote:
> 06.09.25 01:01, Daniel P. Smith:
>> On 9/2/25 05:41, Jan Beulich wrote:
>>> On 01.09.2025 12:52, Sergiy Kibrik wrote:
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -418,6 +418,17 @@ config XSM_FLASK_AVC_STATS
If uns
Hi Sergiy,
If you don't mind, please CC me directly, as I am the only XSM
maintainer for which you will need my Ack. And for whatever reason, I
cannot find the v2 post in my xen-devel folder. If you want to resend me
v2, it would be greatly appreciated.
V/r,
Daniel P. Smith
Apertus Solutions
On 01.09.2025 12:52, Sergiy Kibrik wrote:
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -418,6 +418,17 @@ config XSM_FLASK_AVC_STATS
>
> If unsure, say Y.
>
> +config XSM_FLASK_SIDTABLE_ORDER
> + int "Maximum number of security identifiers (base-2 exponent)" if EXPERT
>
Currently Xen lacks a defined largest number of security IDs it can potentially
use. The number of SIDs are naturally limited by number of security contexts
provided by a given security policy, i.e. how many combination of user, role
and type there can be, and is dependant on the policy being used.
