From: F6BVP <f6bvp@free.fr>
To: netdev <netdev@vger.kernel.org>
Cc: linux-hams@vger.kernel.org, Bernard Pidoux <bernard.pidoux@free.fr>
Subject: kworker/u16 Not tainted
Date: Wed, 20 Aug 2025 21:33:23 +0200 [thread overview]
Message-ID: <3a0b0d29-7cd7-49a9-bb68-a487c996760d@free.fr> (raw)
In-Reply-To: <847a7cd7-c17c-4aa7-824d-22768ff9775d@free.fr>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
[kworker/u16 Not tainted]
kernel panic is occuring in up-to-date net-next kernel as well as with
ALL kernels since linux-6.15.1
As shown in attached picture Oops is always correlated with mkiss.
mkiss driver is used in hamradio communications and in this specific
case it is associated with AX25 and rose drivers in fpac a ROSE/FPAC
network application.
The bug is trigger by a connect request in fpac to a neighbour node
using axudp device created by ax25ipd for IP encapsulation over AX25 frames.
Bernard Pidoux, f6bvp / ai7bg
[-- Attachment #2: Ooops_kworker-6.17.0-rc2_1.jpg --]
[-- Type: image/jpeg, Size: 137888 bytes --]
next prev parent reply other threads:[~2025-08-20 19:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11c5701d-4bf9-4661-ad8a-06690bbe1c1c@free.fr>
[not found] ` <fff0b3eb-ea42-4475-970d-30622dc25dca@free.fr>
2025-08-16 18:45 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops Bernard Pidoux
2025-08-18 10:00 ` Bernard Pidoux
2025-08-18 10:04 ` Folkert van Heusden
2025-08-18 14:19 ` F6BVP
2025-08-18 16:30 ` Dan Cross
2025-08-18 18:28 ` F6BVP
2025-08-18 22:11 ` Dan Cross
2025-08-18 22:31 ` F6BVP
2025-08-20 8:50 ` F6BVP
2025-08-20 19:33 ` F6BVP [this message]
2025-08-21 11:28 ` F6BVP
2025-08-21 17:49 ` F6BVP
2025-08-21 22:39 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops F6BVP
2025-08-22 3:10 ` Folkert van Heusden
2025-08-24 14:04 ` F6BVP
2025-08-25 12:40 ` Dan Carpenter
2025-08-26 13:31 ` F6BVP
2025-08-26 13:36 ` Eric Dumazet
2025-08-27 14:16 ` F6BVP
2025-08-27 17:30 ` Florian Westphal
2025-08-28 16:39 ` F6BVP
2025-08-30 23:37 ` F6BVP
2025-09-01 12:04 ` Eric Dumazet
2025-09-01 12:05 ` Eric Dumazet
[not found] ` <cd0461e0-8136-4f90-df7b-64f1e43e78d4@trinnet.net>
2025-09-01 15:59 ` F6BVP
2025-09-01 16:03 ` Eric Dumazet
2025-09-01 19:10 ` David Ranch
2025-09-01 19:16 ` Eric Dumazet
2025-09-02 7:44 ` F6BVP
2025-09-02 7:55 ` Eric Dumazet
2025-09-03 9:51 ` [BUG] [ROSE] slab-use-after-free in lock_timer_base Bernard Pidoux
2025-09-03 10:01 ` Eric Dumazet
2025-09-03 10:11 ` F6BVP
2025-09-03 11:07 ` Takamitsu Iwai
2025-09-01 19:04 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops David Ranch
2025-09-02 7:54 ` F6BVP
2025-08-19 21:17 ` [OT] " Miroslav Skoric
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=3a0b0d29-7cd7-49a9-bb68-a487c996760d@free.fr \
--to=f6bvp@free.fr \
--cc=bernard.pidoux@free.fr \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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