From: patchwork-bot+netdevbpf@kernel.org
To: Remi Pommarel <repk@triplefau.lt>
Cc: arnd@arndb.de, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
nikolay@nvidia.com, roopa@nvidia.com, kuba@kernel.org,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next] net: bridge: Get SIOCGIFBR/SIOCSIFBR ioctl working in compat mode
Date: Mon, 27 Dec 2021 12:40:09 +0000 [thread overview]
Message-ID: <164060880950.2123.6082560093716021616.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211224114640.29679-1-repk@triplefau.lt>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Dec 2021 12:46:40 +0100 you wrote:
> In compat mode SIOC{G,S}IFBR ioctls were only supporting
> BRCTL_GET_VERSION returning an artificially version to spur userland
> tool to use SIOCDEVPRIVATE instead. But some userland tools ignore that
> and use SIOC{G,S}IFBR unconditionally as seen with busybox's brctl.
>
> Example of non working 32-bit brctl with CONFIG_COMPAT=y:
> $ brctl show
> brctl: SIOCGIFBR: Invalid argument
>
> [...]
Here is the summary with links:
- [net-next] net: bridge: Get SIOCGIFBR/SIOCSIFBR ioctl working in compat mode
https://git.kernel.org/netdev/net-next/c/fd3a45900055
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Remi Pommarel <repk@triplefau.lt>
Cc: netdev@vger.kernel.org, roopa@nvidia.com, nikolay@nvidia.com,
arnd@arndb.de, davem@davemloft.net, kuba@kernel.org,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: bridge: Get SIOCGIFBR/SIOCSIFBR ioctl working in compat mode
Date: Mon, 27 Dec 2021 12:40:09 +0000 [thread overview]
Message-ID: <164060880950.2123.6082560093716021616.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211224114640.29679-1-repk@triplefau.lt>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Dec 2021 12:46:40 +0100 you wrote:
> In compat mode SIOC{G,S}IFBR ioctls were only supporting
> BRCTL_GET_VERSION returning an artificially version to spur userland
> tool to use SIOCDEVPRIVATE instead. But some userland tools ignore that
> and use SIOC{G,S}IFBR unconditionally as seen with busybox's brctl.
>
> Example of non working 32-bit brctl with CONFIG_COMPAT=y:
> $ brctl show
> brctl: SIOCGIFBR: Invalid argument
>
> [...]
Here is the summary with links:
- [net-next] net: bridge: Get SIOCGIFBR/SIOCSIFBR ioctl working in compat mode
https://git.kernel.org/netdev/net-next/c/fd3a45900055
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-12-27 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 11:46 [Bridge] [PATCH net-next] net: bridge: Get SIOCGIFBR/SIOCSIFBR ioctl working in compat mode Remi Pommarel
2021-12-24 11:46 ` Remi Pommarel
2021-12-27 11:55 ` [Bridge] " Nikolay Aleksandrov
2021-12-27 11:55 ` Nikolay Aleksandrov
2021-12-27 12:40 ` patchwork-bot+netdevbpf [this message]
2021-12-27 12:40 ` patchwork-bot+netdevbpf
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=164060880950.2123.6082560093716021616.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=repk@triplefau.lt \
--cc=roopa@nvidia.com \
/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.