From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Stefan Chulski <stefanc@marvell.com>
Cc: Andrew Lunn <andrew@lunn.ch>, "kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Nadav Haklai <nadavh@marvell.com>,
Yan Markman <ymarkman@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mw@semihalf.com" <mw@semihalf.com>,
"atenart@kernel.org" <atenart@kernel.org>,
"rabeeh@solid-run.com" <rabeeh@solid-run.com>
Subject: Re: [EXT] Re: [V2 net-next] net: mvpp2: Add reserved port private flag configuration
Date: Tue, 16 Mar 2021 15:41:29 +0000 [thread overview]
Message-ID: <20210316154129.GO1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <CO6PR18MB38733E25F6B3194D4858147BB06B9@CO6PR18MB3873.namprd18.prod.outlook.com>
On Tue, Mar 16, 2021 at 03:28:51PM +0000, Stefan Chulski wrote:
> No XDP doesn't require this. One of the use cases of the port reservation feature is the Marvell User Space SDK (MUSDK) which its latest code is publicly available here:
> https://github.com/MarvellEmbeddedProcessors/musdk-marvell
> You can find example use case for this application here:
> http://wiki.macchiatobin.net/tiki-index.php?page=MUSDK+Introduction
I really, really hope that someone has thought this through:
Packet Processor I/O Interface (PPIO)
The MUSDK PPIO driver provides low-level network interface API for
User-Space network drivers/applications. The PPIO infrastrcuture maps
Marvell's Packet Processor (PPv2) configuration space and I/O descriptors
space directly to user-space memory. This allows user-space
driver/application to directly process the packet processor I/O rings from
user space, without any overhead of a copy operation.
I realy, really hope that you are not exposing the I/O descriptors to
userspace, allowing userspace to manipulate the physical addresses in
those descriptors, and that userspace is not dealing with physical
addresses.
If userspace has access to the I/O descriptors with physical addresses,
or userspace is dealing with physical addresses, then you can say
good bye to any kind of security on the platform. Essentially, in such
a scenario, the entire system memory becomes accessible to userspace,
which includes the kernel.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-03-16 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 16:43 [V2 net-next] net: mvpp2: Add reserved port private flag configuration stefanc
2021-03-11 16:59 ` Andrew Lunn
2021-03-16 15:28 ` [EXT] " Stefan Chulski
2021-03-16 15:41 ` Russell King - ARM Linux admin [this message]
2021-03-16 16:51 ` Stefan Chulski
2021-03-18 20:53 ` Andrew Lunn
2021-03-22 15:59 ` Stefan Chulski
2021-03-22 16:28 ` Andrew Lunn
2021-03-22 18:24 ` Stefan Chulski
2021-03-11 20:33 ` Jakub Kicinski
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=20210316154129.GO1463@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rabeeh@solid-run.com \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ymarkman@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox