From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Henry Barreto <contato@henrybarreto.dev>,
Richard Weinberger <richard@nod.at>
Cc: Tiwei Bie <tiwei.btw@antgroup.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
Henry Barreto <me@henrybarreto.dev>
Subject: Re: [PATCH] um: vector: avoid NULL queue dereference in legacy RX mode
Date: Thu, 28 May 2026 10:17:50 +0200 [thread overview]
Message-ID: <21c2c12a804d662d74c3518267d90e045223583e.camel@sipsolutions.net> (raw)
In-Reply-To: <a3be3b6c-3347-4b5b-97fa-2431cfb76623@cambridgegreys.com>
On Thu, 2026-05-28 at 09:00 +0100, Anton Ivanov wrote:
> >
> > So ... you're effectively saying that the tap transport has been broken
> > since 6.12, released ~1.5 years ago.
>
> The one I use is raw :) It is the most useful.
Right.
> Tap badly needs someone to expose the socket which the kernel uses to implement it. I started writing a kernel helper at some point, but never finished it. It should be able to produce "stupid speeds" with it.
>
> And, yes indeed, this was broken by 612a8c8e0b43ba7e3d0e51f6f76a5fec4912d439 / 2024-07-05 which by the look of it I did not test for tap.
>
Yeah, I guess I'm just thinking that clearly nobody uses it, the
infrastructure isn't there (as you say), and it was broken for a rather
long time now and nobody complained (that we know of.)
So ... is it worth even keeping it? I'm fine either way, just wondering.
johannes
next prev parent reply other threads:[~2026-05-28 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 21:35 Henry Barreto
2026-05-28 7:13 ` Johannes Berg
2026-05-28 7:31 ` Anton Ivanov
2026-05-28 8:00 ` Anton Ivanov
2026-05-28 8:17 ` Johannes Berg [this message]
2026-05-28 8:21 ` Anton Ivanov
2026-05-28 8:02 ` Anton Ivanov
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=21c2c12a804d662d74c3518267d90e045223583e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=contato@henrybarreto.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=me@henrybarreto.dev \
--cc=richard@nod.at \
--cc=tiwei.btw@antgroup.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®