lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <166393141508.14679.3924285675758726094.git-patchwork-notify@kernel.org> Date: Fri, 23 Sep 2022 11:10:15 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Patrick Rohr <prohr@...gle.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, maze@...gle.com, lorenzo@...gle.com, jasowang@...hat.com, stephen@...workplumber.org, nicolas.dichtel@...nd.com Subject: Re: [PATCH v2] tun: support not enabling carrier in TUNSETIFF Hello: This patch was applied to netdev/net.git (master) by David S. Miller <davem@...emloft.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
Powered by blists - more mailing lists