In the funtion pci_unmap_resource,the requested_addr will be print and this may cause some risks like the code below: void pci_unmap_resource(void *requested_addr, size_t size) { if (requested_addr == NULL) return; /* Unmap the PCI memory resource of device */ if (munmap(requested_addr, size)) { RTE_LOG(ERR, EAL, "%s(): cannot munmap(%p, 0x%lx): %s\n", __func__, requested_addr, (unsigned long)size, strerror(errno)); } else RTE_LOG(DEBUG, EAL, " PCI memory unmapped at %p\n", requested_addr); }
Gaetan, Can you please take a look? Thanks Ajit
Hi, Andy could you please be more specific? What risk do you see? As I see it, the DPDK application is run with the right to map addresses exposed by *IO drivers. A user having the right to see the DPDK app logs would have the same rights to discover those mappings directly from *IO.
Hi Gaetan, I don't think it is a good idea to expose the address in the log,but it is just a risk,we can ignore it.
The issue is that logged messages go to syslog, and there maybe malware that has access to syslog and can use the that message to find addresses for other damage.