> From: Aaron Conole <[email protected]> > Date: Thursday, 16 March 2023 at 13:00 > To: [email protected] <[email protected]> > Cc: Robin Jarry <[email protected]>, Gaetan Rivet <[email protected]>, Ilya > Maximets <[email protected]>, Eli Britstein <[email protected]>, Maxime > Coquelin <[email protected]>, Jason Gunthorpe <[email protected]>, > Majd Dibbiny <[email protected]>, David Marchand <david. > [email protected]>, Simon Horman <[email protected]>, Flavio > Leitner <[email protected]> > Subject: [PATCH v4] dpdk: Allow retaining CAP_SYS_RAWIO privileges > External email: Use caution opening links or attachments > > > Open vSwitch generally tries to let the underlying operating system > managed the low level details of hardware, for example DMA mapping, > bus arbitration, etc. However, when using DPDK, the underlying > operating system yields control of many of these details to userspace > for management. > > In the case of some DPDK port drivers, configuring rte_flow or even > allocating resources may require access to iopl/ioperm calls, which > are guarded by the CAP_SYS_RAWIO privilege on linux systems. These > calls are dangerous, and can allow a process to completely compromise > a system. However, they are needed in the case of some userspace > driver code which manages the hardware (for example, the mlx > implementation of backend support for rte_flow). > > Here, we create an opt-in flag passed to the command line to allow > this access. We need to do this before ever accessing the database, > because we want to drop all privileges asap, and cannot wait for > a connection to the database to be established and functional before > dropping. There may be distribution specific ways to do capability > management as well (using for example, systemd), but they are not > as universal to the vswitchd as a flag. > > Reviewed-by: Simon Horman <[email protected]> > Signed-off-by: Aaron Conole <[email protected]> > ---
Thank you for handling this Aaron, Acked-by: Gaetan Rivet <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
