netdev - Re: [PATCH 1/2] eth phy: add mdio bus char device interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180618072538.GA31732@lunn.ch>
Date:   Mon, 18 Jun 2018 09:25:38 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Wei Li <liwei1412@....com>
Cc:     f.fainelli@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] eth phy: add mdio bus char device interface

1;5202;0cOn Mon, Jun 18, 2018 at 11:32:12AM +0800, Wei Li wrote:
> Add the char device interface of mdio bus, like what i2c-dev or spidev do.
> They make it possible for user-space programs to access the bus directly.
> 

Hi Wei

What is your real use case here? 

What we don't want to do is add an easy to use API to allow vendors to
write user space binary blob propriatary Ethernet switch or PHY
drivers.

Also, it has been agreed that all new API's to the network stack need
to use netlink sockets, not IOCTLs.

The IOCTL interface you provide is very similar to what the stack
already has. Why cannot use you use that?

	Andrew