Thread (2 messages) flat view 2 messages, 2 authors, 2021-01-28

Re: [PATCH v5 net-next] From: Petr Vandrovec <petr@vmware.com>

From: Andrew Lunn <andrew@lunn.ch>
Date: 2021-01-28 02:23:29
Also in: lkml

On Wed, Jan 27, 2021 at 06:08:16PM -0800, Ronak Doshi wrote:
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 <redacted>
Signed-off-by: Ronak Doshi <redacted>
Hi Ronak

The Subject line is still messed up, it contains Petr name rather than
a subject.

	Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help