From: David Ranch <linux-hams@trinnet.net>
To: Lars Kellogg-Stedman <lars@oddbit.com>
Cc: Chris Maness <christopher.maness@gmail.com>,
Duoming Zhou <duoming@zju.edu.cn>,
linux-hams@vger.kernel.org, dan.carpenter@linaro.org
Subject: Re: Kernel 6.9.1 AX.25 Crash
Date: Wed, 22 May 2024 09:10:11 -0700 [thread overview]
Message-ID: <bdcc8a74-2218-6570-eb93-8cfc00b13781@trinnet.net> (raw)
In-Reply-To: <c3infeyajl4hr2tuyfmmccdv4gjbhsulaxuetozigqwqtj4jga@42eucxtsfk2y>
Hello Lars,
> That's good to know! I based that on the amount of traffic I see here on
> the linux-hams list, and the difficulty in getting anybody to offer an
> opinion (or an alternative to) these changes. If there is a more active
> forum where people are talking about Linux and amateur radio I'm happy
> to join there as well.
Just to name a few, consider joining:
Direwolf software-tnc: https://groups.io/g/direwolf
Raspberry Pi HAM Radio: https://groups.io/g/RaspberryPi-4-HamRadio
> I think this would typically be the job of a subsystem maintainer; this
> is another way in which the lack of a maintainer hurts the
> ax.25 stack.
But since there isn't one.. why are these broken commits still being
allowed?
> Have you put together an ax.25 test suite? I put together an automated
> test for the particular problem I'm trying to resolve (that was
> necessary in order to successfully use `git bisect run`); collecting
> these sorts of things in one place would be a great step forward.
I've offered to do so but I never received any response. I need to know
what is needed here:
- Just document various testcase scenarios?
- Create automation to run the test cases? In what language? Bash?
Python? Perl? JavaScript?
- Create a set of pre-configured inter-connected VM images for
running automated tests? If so, what format, what CPU architecture, etc
>> I am hugely grateful to you (Lars) on being able to submit some meaningful
>> fixes and was able to get them committed to the mainline.
>
> Just to clear, that hasn't happened yet! The patch needs to get
> approved first.
Sigh... ok.
>> The next major hurdle that I would love to get feedback on is how to
>> get these new changes but also create a set of backported fixes
>> committed into various Linux distributions kernels that don't strictly
>> follow the mainline kernel. My personal interest is in the Raspberry
>> Pi OS kernel
My primary focus is on Raspberry Pi as well but also X86 computers too.
> I'm running this patch on kernel 6.6.30 on my Raspberry Pi systems; you
> can find the patch against 6.6.30 here:
>
> https://github.com/larsks/ax25-debugging/tree/main/patches-for-6.6.30
>
> It's made my Pis much more stable. I think that if the patch gets
> accepted for the mainline kernel it should be relatively easy to get
> into the Raspberry Pi kernel as well.
Are you patching and compiling the Raspberry Pi OS specific kernel tree
or are you using the mainline Linux-Next or primary Linus tree?
--David
KI6ZHD
next prev parent reply other threads:[~2024-05-22 16:10 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 6:02 [PATCH net] ax25: Fix refcount leak issues of ax25_dev Duoming Zhou
2024-05-01 17:33 ` Markus Elfring
2024-05-01 17:43 ` Dan Carpenter
2024-05-02 4:35 ` duoming
2024-05-02 7:56 ` Dan Carpenter
2024-05-02 9:30 ` Paolo Abeni
2024-05-02 1:29 ` Lars Kellogg-Stedman
2024-05-03 20:36 ` Dan Carpenter
2024-05-03 23:40 ` Lars Kellogg-Stedman
2024-05-04 12:16 ` Dan Carpenter
2024-05-04 22:16 ` Lars Kellogg-Stedman
2024-05-07 3:18 ` Lars Kellogg-Stedman
2024-05-07 8:08 ` Dan Carpenter
2024-05-07 9:04 ` duoming
2024-05-08 18:27 ` Dan Carpenter
2024-05-09 1:40 ` duoming
2024-05-23 12:30 ` Lars Kellogg-Stedman
2024-05-07 6:38 ` Dan Carpenter
2024-05-15 9:52 ` duoming
2024-05-16 19:20 ` Lars Kellogg-Stedman
[not found] ` <CANnsUMHTZ_P4-C2iGdbakcp_Xk5c-aCO5kYEvaBdOcsaSnK5Pg@mail.gmail.com>
2024-05-20 14:42 ` Kernel 6.9.1 AX.25 Crash Lars Kellogg-Stedman
2024-05-20 14:49 ` Chris Maness
2024-05-21 0:11 ` Chris Maness
2024-05-21 0:48 ` Lars Kellogg-Stedman
2024-05-21 1:38 ` Chris Maness
2024-05-21 2:12 ` Dan Cross
2024-05-21 3:07 ` Chris Maness
2024-05-21 11:47 ` Dave Hibberd
2024-05-21 12:03 ` Chris Maness
2024-05-21 19:20 ` Mike Quin
2024-05-21 23:02 ` Chris Maness
2024-05-21 23:07 ` Mike Quin
2024-05-21 23:17 ` Chris Maness
2024-05-21 15:53 ` David Ranch
2024-05-21 16:28 ` Chris Maness
2024-05-21 18:12 ` Lars Kellogg-Stedman
2024-05-22 15:32 ` Dan Cross
2024-05-22 16:07 ` Chris Maness
2024-05-22 17:06 ` David Ranch
2024-05-22 18:04 ` Dan Cross
2024-05-22 17:54 ` Dan Cross
2024-05-22 18:17 ` Lars Kellogg-Stedman
2024-05-22 18:37 ` Dan Cross
2024-05-22 19:23 ` Lars Kellogg-Stedman
2024-05-22 22:22 ` David Ranch
2024-05-22 22:32 ` Lars Kellogg-Stedman
2024-05-23 0:54 ` Userspace AX.25 stack library [was Re: Kernel 6.9.1 AX.25 Crash] Stuart Longland VK4MSL
2024-05-23 16:32 ` Dan Cross
2024-05-22 16:10 ` David Ranch [this message]
2024-05-22 18:13 ` Kernel 6.9.1 AX.25 Crash Lars Kellogg-Stedman
2024-06-07 12:01 ` Lars Kellogg-Stedman
2024-06-07 13:49 ` David Ranch
2024-06-08 1:59 ` Lars Kellogg-Stedman
2024-06-08 15:23 ` David Ranch
2024-05-23 10:30 ` Dan Carpenter
2024-05-27 17:59 ` Chris Maness
2024-05-04 11:04 ` [PATCH net] ax25: Fix refcount leak issues of ax25_dev Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 2:55 Kernel 6.9.1 AX.25 Crash Chris Maness
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=bdcc8a74-2218-6570-eb93-8cfc00b13781@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=christopher.maness@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=duoming@zju.edu.cn \
--cc=lars@oddbit.com \
--cc=linux-hams@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