mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Umang Pokhriyal <umangpokhriyall@gmail.com>,
	 Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: 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 v2] tap: report IFF_DETACH_QUEUE in TUNGETIFF
Date: Mon, 05 Oct 2026 13:15:34 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.2caa30c4a0ad5@gmail.com> (raw)
In-Reply-To: <20261005061236.22907-1-umangpokhriyall@gmail.com>

Umang Pokhriyal wrote:
> Willem de Bruijn wrote:
> > I suppose we want tap to expose this state through TUNGETIFF, like tun,
> > because applications already use that?
> 
> Yes. CRIU reads IFF_DETACH_QUEUE from TUNGETIFF when it dumps a tun
> file, and Cloud Hypervisor did the same until it found that macvtap
> reports every queue as attached. Code written for tun's queue API gets
> the wrong answer on macvtap, even though macvtap accepts the same
> TUNSETQUEUE.
> 
> > Else cleaner than working around bits would be a whole new TUNGETQUEUE
> > call to match TUNSETQUEUE. Rather than to squish this into TUNGETIFF,
> > while that has no equivalent in TUNSETIFF.
> >
> > But, that approach does not help existing applications.
> 
> Right, those applications would have to be changed to use a new
> TUNGETQUEUE.
> 
> Thanks for taking another look.

Thanks for verifying.

Reviewed-by: Willem de Bruijn <willemb@google.com>


      reply	other threads:[~2026-10-05 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 17:47 Umang Pokhriyal
2026-10-04 22:52 ` Willem de Bruijn
2026-10-05  6:12   ` Umang Pokhriyal
2026-10-05 17:15     ` Willem de Bruijn [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=willemdebruijn.kernel.2caa30c4a0ad5@gmail.com \
    --to=willemdebruijn.kernel@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@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=umangpokhriyall@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®