From: Andrew Lunn <andrew@lunn.ch>
To: Ronak Doshi <doshir@vmware.com>
Cc: netdev@vger.kernel.org, Petr Vandrovec <petr@vmware.com>,
"maintainer:VMWARE VMXNET3 ETHERNET DRIVER"
<pv-drivers@vmware.com>, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 net-next] From: Petr Vandrovec <petr@vmware.com>
Date: Thu, 28 Jan 2021 03:20:52 +0100 [thread overview]
Message-ID: <YBIfhK1Kayf6kS62@lunn.ch> (raw)
In-Reply-To: <20210128020816.31318-1-doshir@vmware.com>
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 <petr@vmware.com>
> Signed-off-by: Ronak Doshi <doshir@vmware.com>
Hi Ronak
The Subject line is still messed up, it contains Petr name rather than
a subject.
Andrew
prev parent reply other threads:[~2021-01-28 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 2:08 [PATCH v5 net-next] From: Petr Vandrovec <petr@vmware.com> Ronak Doshi
2021-01-28 2:20 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YBIfhK1Kayf6kS62@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petr@vmware.com \
--cc=pv-drivers@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.