From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from trinity3.trinnet.net (trinity.trinnet.net [96.78.144.185]) by smtp.subspace.kernel.org (Postfix) with ESMTP id AAEC013E03E for ; Wed, 22 May 2024 16:10:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=96.78.144.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716394225; cv=none; b=D5Vvmu3YTkcKcmkVK+jdBkdxYVqxEFADPK0zf2aOf0XfsMy7x0t9PaDeG+FdOnFXjbLO8WHf4CSWOWs4vhGgTGq6Hm8NxDATpsId3gCoyMN39+SoDl67UK43stqh1Arl2jZA2FnfysCJJ5dvIfGOUWJgUCKZrMN1Z8DOmZt/1Gg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716394225; c=relaxed/simple; bh=V6NbfnhpthY+Xzo+nEnldjNDyqdNeWO9/NCXuw5TF3Q=; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version: In-Reply-To:Content-Type; b=sioVsyPrmwbd+O89ToMKkkDrUDB5bpRW/kNSFvnUIGs4672KW/RvsmPvzFFCBiSd7x40T0JnSJRBCH1m2s8Ibyhglu+PahKDp1FK2fN5ieC1W3rWcIVOYZkl619hBkec0LvcNOpvbEsAQKVWq1APS52DN9U6JGf7uVUYHk008kw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=trinnet.net; spf=pass smtp.mailfrom=trinnet.net; arc=none smtp.client-ip=96.78.144.185 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=trinnet.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=trinnet.net Received: from trinity4.trinnet.net (trinity4.trinnet.net [192.168.0.11]) by trinity3.trinnet.net (TrinityOS hardened/TrinityOS Hardened) with ESMTP id 44MGABY8029899; Wed, 22 May 2024 09:10:11 -0700 Subject: Re: Kernel 6.9.1 AX.25 Crash To: Lars Kellogg-Stedman References: <20240501060218.32898-1-duoming@zju.edu.cn> <4it3k7z5sylbv4agiztmwdhaudo2orccpm5pbi24bsu6fyajfm@k3zulkrpqaof> Cc: Chris Maness , Duoming Zhou , linux-hams@vger.kernel.org, dan.carpenter@linaro.org From: David Ranch Message-ID: Date: Wed, 22 May 2024 09:10:11 -0700 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Precedence: bulk X-Mailing-List: linux-hams@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (trinity3.trinnet.net [192.168.0.1]); Wed, 22 May 2024 09:10:12 -0700 (PDT) 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