From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Denys Fedoryshchenko <denys@visp.net.lb>, netdev@vger.kernel.org
Subject: Re: sysfs^H^H^H^H^Hsysctl warnings, reserved names
Date: Sun, 19 Feb 2012 13:11:41 -0800 [thread overview]
Message-ID: <m1aa4e5y0i.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1329483934.2861.12.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (Eric Dumazet's message of "Fri, 17 Feb 2012 14:05:34 +0100")
Eric Dumazet <eric.dumazet@gmail.com> writes:
>> Well we are talking about sysctl not sysfs but same difference, I keep
>> an on eye on them.
>>
>> I expect renaming a network device to "all" or "default" would be a
>> problem in any kernel supporting renaming of networking devices.
>>
>> At the basic level of handling it. sysctl checks for this sometimes
>> now and as soon as my sysctl tree is merged the checks will become
>> unconditionally present. In what sense were you thinking it would
>> be better to address this in the sysctl?
>>
>
> Because problem is : it seems a rename() of "eth3" to "default" is
> allowed by sysctl, yet "default" is already in directory.
>
> It seems sysfs_rename_link() / sysfs_rename_dir() / sysfs_rename() might
> have a problem ?
The files are under /proc/sys so we are talking about sysctls, which
means that the error is reported from register_net_sysctl_table.
The path is:
NETDEV_CHANGENAME
devinet_sysctl_unregister() -> void
devinet_sysctl_register() -> void
return NOTIFY_DONE;
Eric
prev parent reply other threads:[~2012-02-19 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 10:14 sysfs warnings, reserved names Denys Fedoryshchenko
2012-02-17 10:37 ` Eric Dumazet
2012-02-17 11:03 ` Eric Dumazet
2012-02-17 12:07 ` sysfs^H^H^H^H^Hsysctl " Eric W. Biederman
2012-02-17 13:05 ` Eric Dumazet
2012-02-19 21:11 ` Eric W. Biederman [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=m1aa4e5y0i.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=denys@visp.net.lb \
--cc=eric.dumazet@gmail.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