From: Richard Weinberger <richard@nod.at>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Stephen Hemminger <stephen@networkplumber.org>,
manty@debian.org
Subject: bridge-utils: wrong sysfs path odds
Date: Wed, 25 Nov 2015 01:15:15 +0100 [thread overview]
Message-ID: <5654FD93.1070706@nod.at> (raw)
Hi!
Today I was hunting down an issue where "brctl stp br0 off"
always failed on mips64be with n32 userland.
It turned out that the ioctl(fd, SIOCDEVPRIVATE, &ifr) with BRCTL_SET_BRIDGE_STP_STATE
returned -EOPNOTSUPP.
First I thought that this is a plain ABI issue on mips as in old_dev_ioctl()
the ioctl() argument was 0x1 instead of the expected BRCTL_SET_BRIDGE_STP_STATE (0x14)
Further investigation showed that brctl first tries to open the sysfs file
"/sys/class/net/br0/stp_state" and falls back to the legacy ioctl() upon failure.
On my mips setup old_dev_ioctl() seems not to work. And the function's comment
is correct:
/*
* Legacy ioctl's through SIOCDEVPRIVATE
* This interface is deprecated because it was too difficult to
* to do the translation for 32/64bit ioctl compatibility.
*/
Later I've realized that the sysfs path is wrong, the "bridge/" directory
part is missing.
On most setups nobody would notice as the fallback ioctl() works.
Debian's bridge-utils package carries a patch which fixes the sysfs paths.
Can we please have this patch also in upstream bridge-utils?
Thanks,
//richard
next reply other threads:[~2015-11-25 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 0:15 Richard Weinberger [this message]
2015-11-25 0:24 ` bridge-utils: wrong sysfs path odds Richard Weinberger
2015-11-25 0:37 ` Stephen Hemminger
2015-11-25 0:40 ` Richard Weinberger
2015-11-25 9:21 ` Richard Weinberger
[not found] ` <CAJk_L2GSvNUGiexawakMHdm+v5ndv=qLXB9TD7xxn7z9c-ZMsg@mail.gmail.com>
2015-11-25 22:37 ` Richard Weinberger
2015-11-25 22:44 ` Fwd: " Santiago Garcia Mantinan
2015-11-25 22:38 ` Florian Fainelli
2015-11-25 22:41 ` Richard Weinberger
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=5654FD93.1070706@nod.at \
--to=richard@nod.at \
--cc=manty@debian.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.