summaryrefslogtreecommitdiff
path: root/scripts/tracing
diff options
context:
space:
mode:
authorRonak Doshi <doshir@vmware.com>2021-01-28 05:08:16 +0300
committerJakub Kicinski <kuba@kernel.org>2021-01-30 08:07:03 +0300
commitde1da8bcf40564a2adada2d5d5426e05355f66e8 (patch)
tree947f76c45089f8a1a83f8ce1c4680ea0cfcb0f45 /scripts/tracing
parent6c13d75beee5313a38adab7e14365724e301886f (diff)
downloadlinux-de1da8bcf40564a2adada2d5d5426e05355f66e8.tar.xz
vmxnet3: Remove buf_info from device accessible structures
buf_info structures in RX & TX queues are private driver data that do not need to be visible to the device. Although there is physical address and length in the queue descriptor that points to these structures, their layout is not standardized, and device never looks at them. So lets allocate these structures in non-DMA-able memory, and fill physical address as all-ones and length as zero in the queue descriptor. That should alleviate worries brought by Martin Radev in https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20210104/022829.html that malicious vmxnet3 device could subvert SVM/TDX guarantees. Signed-off-by: Petr Vandrovec <petr@vmware.com> Signed-off-by: Ronak Doshi <doshir@vmware.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/tracing')
0 files changed, 0 insertions, 0 deletions