[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230307140535.32ldprkyblpmicjg@skbuf>
Date: Tue, 7 Mar 2023 16:05:35 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Michael Walle <michael@...le.cc>, sean.anderson@...o.com,
davem@...emloft.net, edumazet@...gle.com, f.fainelli@...il.com,
hkallweit1@...il.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, linux@...linux.org.uk,
netdev@...r.kernel.org, pabeni@...hat.com, tobias@...dekranz.com
Subject: Re: [PATCH net-next] net: mdio: Add netlink interface
On Tue, Mar 07, 2023 at 02:49:27PM +0100, Andrew Lunn wrote:
> On Tue, Mar 07, 2023 at 12:23:07PM +0100, Michael Walle wrote:
> > > To prevent userspace phy drivers, writes are disabled by default, and can
> > > only be enabled by editing the source.
> >
> > Maybe we can just taint the kernel using add_taint()? I'm not sure if
> > that will prevent vendors writing user space drivers. Thoughts?
>
> I was thinking about taint as well. But keep the same code structure,
> you need to edit it to enable write.
But as per the commit message, this locks us out of the following
legitimate uses:
- C45-over-C22 (reads)
- Atomic (why only atomic?) (read) access to paged registers
are we ok with the implications?
Powered by blists - more mailing lists