From: patchwork-bot+netdevbpf@kernel.org
To: Patrick Rohr <prohr@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, maze@google.com,
lorenzo@google.com, jasowang@redhat.com,
stephen@networkplumber.org, nicolas.dichtel@6wind.com
Subject: Re: [PATCH v2] tun: support not enabling carrier in TUNSETIFF
Date: Fri, 23 Sep 2022 11:10:15 +0000 [thread overview]
Message-ID: <166393141508.14679.3924285675758726094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220920194825.31820-1-prohr@google.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 20 Sep 2022 12:48:25 -0700 you wrote:
> This change adds support for not enabling carrier during TUNSETIFF
> interface creation by specifying the IFF_NO_CARRIER flag.
>
> Our tests make heavy use of tun interfaces. In some scenarios, the test
> process creates the interface but another process brings it up after the
> interface is discovered via netlink notification. In that case, it is
> not possible to create a tun/tap interface with carrier off without it
> racing against the bring up. Immediately setting carrier off via
> TUNSETCARRIER is still too late.
>
> [...]
Here is the summary with links:
- [v2] tun: support not enabling carrier in TUNSETIFF
https://git.kernel.org/netdev/net/c/195624d9c26b
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:[~2022-09-23 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 23:45 [PATCH] tun: support not enabling carrier in TUNSETIFF Patrick Rohr
2022-09-16 23:54 ` Maciej Żenczykowski
2022-09-19 6:52 ` Jason Wang
2022-09-19 17:18 ` Stephen Hemminger
2022-09-20 0:01 ` Maciej Żenczykowski
2022-09-20 1:44 ` Jason Wang
2022-09-20 15:36 ` Stephen Hemminger
2022-09-20 19:48 ` [PATCH v2] " Patrick Rohr
2022-09-20 21:47 ` Maciej Żenczykowski
2022-09-21 2:53 ` Jason Wang
2022-09-21 6:35 ` Nicolas Dichtel
2022-09-23 11:10 ` patchwork-bot+netdevbpf [this message]
2022-09-20 7:35 ` [PATCH] " Nicolas Dichtel
2022-09-21 7:08 ` [tun] a4d8f18ebc: ltp.ioctl03.fail kernel test robot
2022-09-21 7:48 ` [LTP] " Cyril Hrubis
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=166393141508.14679.3924285675758726094.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=prohr@google.com \
--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 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).