From: F6BVP <f6bvp@free.fr>
To: Eric Dumazet <edumazet@google.com>
Cc: David Ranch <linux-hams@trinnet.net>,
Paolo Abeni <pabeni@redhat.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
linux-hams@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Dan Cross <crossd@gmail.com>,
Folkert van Heusden <folkert@vanheusden.com>,
Florian Westphal <fw@strlen.de>
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Date: Tue, 2 Sep 2025 09:44:56 +0200 [thread overview]
Message-ID: <e901a424-fe95-4adc-9777-31d54464d2c5@free.fr> (raw)
In-Reply-To: <CANn89iJGdn2J-UwK9ux+m9r8mRhAND_t2kU6mLCs=RszBhCyRA@mail.gmail.com>
I tested the fix and validated it on different kernels versions.
All are doing fine : 6.14.11 , 6.15.11, 6.16.4
Congratulations and many thanks to Eric Dumazet for spending his time on
repairing AX25 mkiss serial connexions.
Hamradio fans will be able to continue experimenting with AX25 using
next Linux developments.
Bernard Pidoux
F6BVP / AI7BG
http://radiotelescope-lavillette.fr
Le 01/09/2025 à 18:03, Eric Dumazet a écrit :
> Keep calm, I am just saying that the bisection pointed to a fine commit,
> but it took a _lot_ of time to root-cause the issue.
>
> And the bug is in ax25, not in Paolo patch.
>
> Please test the fix, and thank me for actually working on a fix, while
> I have more urgent work on my plate.
next prev parent reply other threads:[~2025-09-02 7:45 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 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops 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 [this message]
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=e901a424-fe95-4adc-9777-31d54464d2c5@free.fr \
--to=f6bvp@free.fr \
--cc=crossd@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=edumazet@google.com \
--cc=folkert@vanheusden.com \
--cc=fw@strlen.de \
--cc=linux-hams@trinnet.net \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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