public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dan Cross <crossd@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	corbet@lwn.net, skhan@linuxfoundation.org,
	federico.vaga@vaga.pv.it, carlos.bilbao@kernel.org,
	avadhut.naik@amd.com, alexs@kernel.org, si.yanteng@linux.dev,
	dzm91@hust.edu.cn, 2023002089@link.tyut.edu.cn,
	tsbogend@alpha.franken.de, dsahern@kernel.org,
	jani.nikula@intel.com, mchehab+huawei@kernel.org,
	gregkh@linuxfoundation.org, jirislaby@kernel.org, tytso@mit.edu,
	herbert@gondor.apana.org.au, ebiggers@kernel.org,
	johannes.berg@intel.com, geert@linux-m68k.org,
	pablo@netfilter.org, tglx@kernel.org, mashiro.chen@mailbox.org,
	mingo@kernel.org, dqfext@gmail.com, jreuter@yaina.de,
	sdf@fomichev.me, pkshih@realtek.com, enelsonmoore@gmail.com,
	mkl@pengutronix.de, toke@toke.dk, kees@kernel.org,
	jlayton@kernel.org, wangliang74@huawei.com, aha310510@gmail.com,
	takamitz@amazon.co.jp, kuniyu@google.com,
	linux-doc@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH net-deletions] net: remove ax25 and amateur radio (hamradio) subsystem
Date: Tue, 21 Apr 2026 10:14:00 -0700	[thread overview]
Message-ID: <20260421101400.67545b20@phoenix.local> (raw)
In-Reply-To: <CAEoi9W6ZRw6aEh62Xbgkg-TW8URHbVp6dHTT9krFiTkotjTuTA@mail.gmail.com>

On Tue, 21 Apr 2026 12:17:23 -0400
Dan Cross <crossd@gmail.com> wrote:

> On Tue, Apr 21, 2026 at 9:55 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> > On Mon, 20 Apr 2026 19:18:23 -0700
> > Jakub Kicinski <kuba@kernel.org> wrote:  
> > > Remove the amateur radio (AX.25, NET/ROM, ROSE) protocol implementation
> > > and all associated hamradio device drivers from the kernel tree.
> > > This set of protocols has long been a huge bug/syzbot magnet,
> > > and since nobody stepped up to help us deal with the influx
> > > of the AI-generated bug reports we need to move it out of tree
> > > to protect our sanity.
> > >
> > > The code is moved to an out-of-tree repo:
> > > https://github.com/linux-netdev/mod-orphan
> > > if it's cleaned up and reworked there we can accept it back.  
> >
> > It would be good if these protocols could be done in userspace
> > or with BPF?  
> 
> Consensus for a userspace implementation is what folks on linux-hams
> seem to be converging on.
> 
> The amateur radio protocols are more or less specific to low-speed
> links, they are not particularly coupled to anything else that
> requires running in the kernel, and the main coupling point (IP over
> AX.25) can be implemented via TAP/TUN.
> 
> There are several popular packages that already implement AX.25 and
> NET/ROM in user-space (for the interested, LinBPQ seems to be the
> canonical example).  The main missing piece is ROSE, but it is likely
> easier to add that to an existing package, or potentially something
> brand new, than keep it in the kernel.
> 
> There's no compelling reason to keep these protocols in the kernel,
> whether in-tree or out-of-tree; at least, one has not been
> articulated.
> 
>         - Dan C.

Thanks, my other concern is carrying support for these in ip commands.
If not kernel based, then iproute2 doesn't need to worry.

  reply	other threads:[~2026-04-21 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  2:18 [PATCH net-deletions] net: remove ax25 and amateur radio (hamradio) subsystem Jakub Kicinski
2026-04-21  6:04 ` Greg KH
2026-04-21 13:45 ` Stephen Hemminger
2026-04-21 13:55 ` Stephen Hemminger
2026-04-21 16:17   ` Dan Cross
2026-04-21 17:14     ` Stephen Hemminger [this message]
2026-04-21 17:47       ` Dan Cross

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=20260421101400.67545b20@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=aha310510@gmail.com \
    --cc=alexs@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=avadhut.naik@amd.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=crossd@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=dzm91@hust.edu.cn \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=federico.vaga@vaga.pv.it \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=jani.nikula@intel.com \
    --cc=jirislaby@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=johannes.berg@intel.com \
    --cc=jreuter@yaina.de \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mashiro.chen@mailbox.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=pkshih@realtek.com \
    --cc=sdf@fomichev.me \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=takamitz@amazon.co.jp \
    --cc=tglx@kernel.org \
    --cc=toke@toke.dk \
    --cc=tsbogend@alpha.franken.de \
    --cc=tytso@mit.edu \
    --cc=wangliang74@huawei.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