[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7d690606-7abe-42db-80d4-2ef979e8303b@moroto.mountain>
Date: Mon, 22 Apr 2024 16:04:13 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Jeongjun Park <aha310510@...il.com>
Cc: kuba@...nel.org, linux-hams@...r.kernel.org,
linux-kernel@...r.kernel.org,
syzbot+8e03da5d64bc85098811@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH net,v3] net: hams: Fix deadlock caused by unsafe-irq lock
in sp_get()
The ealier versions didn't build. I feel like switching from _irqsave()
to _irq() was wrong but you just did it because you couldn't figure out
how to make _irqsave() compile...
On Sat, Apr 20, 2024 at 05:21:02PM +0900, Jeongjun Park wrote:
> After looking at this email and testing everything, I have confirmed
> that both patches are running without any problems in my environment,
> and the patchwork test outputs an unknown error in the patch
> in ap_get().
What does "the patchwork test outputs an unknown error in the patch in
ap_get()" mean?
>
> But the patch for sp_get() is confirmed to have no problem,
> can you tell me more about the problem?
>
> Thanks.
You say that it was tested but syzbot says that it doesn't have a
reproducer for this warning.
regards,
dan carpenter
Powered by blists - more mailing lists