From: Umang Pokhriyal <umangpokhriyall@gmail.com>
To: netdev-bot+sashiko@kernel.org
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowangio@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tap: report IFF_DETACH_QUEUE in TUNGETIFF
Date: Sun, 4 Oct 2026 23:02:23 +0530 [thread overview]
Message-ID: <20261004173224.33809-1-umangpokhriyall@gmail.com> (raw)
In-Reply-To: <179087539624.434549.6585301310404315341@kernel.org>
On Thu, Oct 01, 2026 at 05:23:16PM +0000, netdev-bot+sashiko@kernel.org wrote:
> [Severity: Medium]
> Can this break a read-modify-write of TUNGETIFF and TUNSETIFF on a
> detached queue?
Yes. tap accepts TUNSETIFF on a bound fd and tun does not, so only tap
has this round trip. v2 will ignore IFF_DETACH_QUEUE in TUNSETIFF.
> [Severity: Low]
> If it is meant as feature parity for net-next, could the commit message
> say so instead of calling it a bug?
It is meant as parity with tun for net-next. v2 will say so.
pw-bot: cr
prev parent reply other threads:[~2026-10-04 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 14:22 Umang Pokhriyal
2026-09-30 15:02 ` Willem de Bruijn
2026-10-01 17:23 ` netdev-bot+sashiko
2026-10-04 17:32 ` Umang Pokhriyal [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=20261004173224.33809-1-umangpokhriyall@gmail.com \
--to=umangpokhriyall@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®