netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Andrew Lunn" <andrew@lunn.ch>,
	"Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: Netdev <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] net: phy: realtek: fix RTL8201F sysfs name
Date: Mon, 5 Nov 2018 18:24:08 -0800	[thread overview]
Message-ID: <5512a79e-2c49-5360-274d-24c509ecd751@gmail.com> (raw)
In-Reply-To: <20181104184346.GA27023@lunn.ch>



On 11/4/2018 10:43 AM, Andrew Lunn wrote:
> On Sun, Nov 04, 2018 at 07:02:42PM +0100, Holger Hoffstätte wrote:
>> Since 4.19 the following error in sysfs has appeared when using the
>> r8169 NIC driver:
>>
>> $cd /sys/module/realtek/drivers
>> $ls -l
>> ls: cannot access 'mdio_bus:RTL8201F 10/100Mbps Ethernet': No such file or directory
>> [..garbled dir entries follow..]
>>
>> Apparently the forward slash in "10/100Mbps Ethernet" is interpreted
>> as directory separator that leads nowhere, and was introduced in commit
>> 513588dd44b ("net: phy: realtek: add RTL8201F phy-id and functions").
>>
>> Fix this by removing the offending slash in the driver name.
>>
>> Other drivers in net/phy seem to have the same problem, but I cannot
>> test/verify them.
>>
>> Signed-off-by: Holger Hoffstätte <holger@applied-asynchrony.com>
> 
> Fixes:513588dd44b ("net: phy: realtek: add RTL8201F phy-id and functions").
> 
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> 
> David, please apply to net.

We should probably seek a more generic solution within sysfs to deny
specific problematic characters from being used, such as ., .., / etc.
-- 
Florian

  reply	other threads:[~2018-11-06 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04 18:02 [PATCH] net: phy: realtek: fix RTL8201F sysfs name Holger Hoffstätte
2018-11-04 18:43 ` Andrew Lunn
2018-11-06  2:24   ` Florian Fainelli [this message]
2018-11-04 18:47 ` Andrew Lunn
2018-11-05  0:44   ` David Miller

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=5512a79e-2c49-5360-274d-24c509ecd751@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=holger@applied-asynchrony.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).