[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260120160008.2kylsycgrpzcwvak@inspiron>
Date: Tue, 20 Jan 2026 21:30:08 +0530
From: Prithvi <activprithvi@...il.com>
To: dranch@...nnet.net, f6bvp@...e.fr
Cc: davem@...emloft.net, edumazet@...gle.com, horms@...nel.org,
kuba@...nel.org, linux-hams@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
pabeni@...hat.com,
syzbot+3f2d46b6e62b8dd546d3@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: Testing for netrom: fix memory leak in nr_add_node
On Mon, Jan 19, 2026 at 07:37:07PM -0800, David Ranch wrote:
>
> Thanks for catching that Bernard and I sure wish kernel committers would
> test their code before committing it! Does the kernel show any sort of
> diagnostic information before it resets? An oops on the serial console,
> etc?
>
> --David
> KI6ZHD
>
>
> On 01/19/2026 01:06 PM, F6BVP wrote:
> >
> > Proposed patch is lethal to netrom module and kernel causing a reboot
> > after a few minutes running ROSE / FPAC node f6bvp.
> >
> > Bernard, f6bvp
> >
>
Hello Bernard and David,
Thank you very much for your feedback. I sincerely apologize for the
instability caused due to this patch. I take this instability very
seriously.
Unfortunately I am on a low-end backup system right now which does not have
resources to build or boot custom kernels effectively, locally. That's why,
it has been difficult for me to test the patch locally due to which I have
been relying on syzbot for testing. I am grateful for your feedback by
testing that patch on your setup.
I will work on investigating further why the kernel isn't stable with this
patch and try to create a better fix for this bug.
Thanks a lot Bernard for testing this patch. In case you get any crash
dump or similar information, it would be very helpful to understand the issue
and fix it.
Thank you very much and best regards,
Prithvi
Powered by blists - more mailing lists