From: F6BVP <f6bvp@free.fr>
To: linux-hams@vger.kernel.org, netdev <netdev@vger.kernel.org>
Cc: Dan Cross <crossd@gmail.com>,
Folkert van Heusden <folkert@vanheusden.com>,
David Ranch <dranch@trinnet.net>
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Date: Thu, 21 Aug 2025 13:28:08 +0200 [thread overview]
Message-ID: <90efee88-b9dc-4f87-86f2-6ab60701c39f@free.fr> (raw)
In-Reply-To: <4e4c9952-e445-41af-8942-e2f1c24a0586@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Hi,
I confirm that linux-6.14 branch up to linux-6.14.11 is fine while ALL
following kernels Oops with kernel panics when using mkiss driver for AX25.
I did not find how to see changes from 6.14.11 to 6.15.1 that Oops !
Having read that 6.15.1 should not be used and be replaced by 6.15.2, I
maked and installed it and found something more interesting during
kernel panics.
Actually a new event is triggered by mkiss. As shown in attached picture
new kind of message says :
Workqueue: event_unbound flush_to_ldisc
RIP: 0010:__netif_receive_skb_core.constprop.0+0x1051/0x1330
I grepped kernel net files and found netif_receive_skb_core in /core/dev.c
Could it be that the bug is inside this function when receiving some
kind of unexpected buffer from mkiss ?
Not being a software engineer (I was actually MD before retiring at 75
from université Pitie-Salpetriere associate professor and hospital...),
I need some help to perform further investigations.
Bernard,
hamradio f6bvp /ai7bg
[-- Attachment #2: netif_receive_6.15.2-1.jpg --]
[-- Type: image/jpeg, Size: 173845 bytes --]
next prev parent reply other threads:[~2025-08-21 11:28 UTC|newest]
Thread overview: 39+ 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 ` kworker/u16 Not tainted F6BVP
2025-08-21 11:28 ` F6BVP [this message]
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
2025-08-16 17:02 Bernard Pidoux
2025-08-16 17:35 ` David Ranch
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=90efee88-b9dc-4f87-86f2-6ab60701c39f@free.fr \
--to=f6bvp@free.fr \
--cc=crossd@gmail.com \
--cc=dranch@trinnet.net \
--cc=folkert@vanheusden.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.