Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Bernard Pidoux F6BVP <bernard.f6bvp@gmail.com>
To: kuba@kernel.org
Cc: toke@toke.dk, stable@vger.kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, pabeni@redhat.com,
	gregkh@linuxfoundation.org, linux-hams@vger.kernel.org
Subject: Re: [PATCH net-deletions] net: remove ax25 and amateur radio (hamradio) subsystem
Date: Sat, 16 May 2026 13:33:55 +0200	[thread overview]
Message-ID: <20260516113355.24110-1-bernard.f6bvp@gmail.com> (raw)

On Fri, 16 May 2026 Jakub Kicinski wrote:
> It's a GitHub repo so PR is probably appropriate there.

Done. I have submitted the five rose fixes as a pull request to the
mod-orphan repository:

  https://github.com/linux-netdev/mod-orphan/pull/1

The PR contains six commits:

  1. rose: build with hamradio_compat.h on pre-7.0 kernels
     (compat shim for struct sockaddr_unsized, required by af_rose.c)
  2. rose: fix dev_put() leak in rose_loopback_timer()
  3. rose: hold loopback neighbour reference across timer callback
  4. rose: fix race between loopback timer and module removal
  5. rose: clear neighbour pointer after rose_neigh_put() in state machines
  6. rose: guard rose_neigh_put() against NULL in timer expiry

All five fixes have been built and tested successfully against kernel
6.17.0-23-generic (pre-7.0): insmod, functional operation, and rmmod
all completed cleanly with no crash or leak detected.

73 de Bernard Pidoux F6BVP

             reply	other threads:[~2026-05-16 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 11:33 Bernard Pidoux F6BVP [this message]
     [not found] <87se8mytvv.fsf@toke.dk>
2026-05-12 14:42 ` [PATCH net-deletions] net: remove ax25 and amateur radio (hamradio) subsystem f6bvp
2026-05-12 14:45 ` f6bvp
2026-05-12 23:36   ` Jakub Kicinski
     [not found]     ` <CAFAa3YDcBsCnEJ1t+a3iHhzxW65HX+QNkZWPKHvDYp_V+UwZYQ@mail.gmail.com>
2026-05-16  1:14       ` Jakub Kicinski
2026-05-16 10:48         ` Bernard Pidoux
2026-05-16 10:55         ` Bernard Pidoux

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=20260516113355.24110-1-bernard.f6bvp@gmail.com \
    --to=bernard.f6bvp@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=toke@toke.dk \
    /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