Jason Andryuk de819c96c8 flask/label-pci: Allow specifying optional irq label ...

IRQs can be shared between devices, so using the same label as the PCI
device can create conflicts where the IRQ is labeled with one of the
device labels preventing assignment of the second device to the second
domain.  Add the ability to specify an irq label distinct from the PCI
device, so a shared irq label can be specified.  The policy would then
be written such that the two domains can each use the shared IRQ type in
addition to their labeled PCI device.  That way we can still label most
of the PCI device resources and assign devices in the face of shared
IRQs.

Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
Reviewed-by: Daniel P. Smith <dpsmith@apertussolutions.com>

2023-03-14 10:46:00 +01:00

..

get-bool.c

tools/flask: remove libflask

2012-02-06 05:03:32 -08:00

getenforce.c

tools/flask: remove libflask

2012-02-06 05:03:32 -08:00

label-pci.c

flask/label-pci: Allow specifying optional irq label

2023-03-14 10:46:00 +01:00

loadpolicy.c

loadpolicy: only close polFd if it is valid

2016-02-29 10:48:49 -05:00

Makefile

tools: Remove -Werror everywhere else

2022-10-14 16:17:41 +01:00

set-bool.c

tools/flask: remove libflask

2012-02-06 05:03:32 -08:00

setenforce.c

tools/flask: remove libflask

2012-02-06 05:03:32 -08:00