From: Dan Carpenter <dan.carpenter@linaro.org>
To: Jeongjun Park <aha310510@gmail.com>
Cc: kuba@kernel.org, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+8e03da5d64bc85098811@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH net,v3] net: hams: Fix deadlock caused by unsafe-irq lock in sp_get()
Date: Mon, 22 Apr 2024 16:04:13 +0300 [thread overview]
Message-ID: <7d690606-7abe-42db-80d4-2ef979e8303b@moroto.mountain> (raw)
In-Reply-To: <20240420082102.63841-1-aha310510@gmail.com>
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
prev parent reply other threads:[~2024-04-22 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 17:32 [syzbot] [hams?] possible deadlock in serial8250_console_write syzbot
2024-04-19 17:43 ` [PATCH v2] net: hams: Fix deadlock caused by unsafe-irq lock in sp_get() Jeongjun Park
2024-04-19 19:14 ` [PATCH net,v3] " Jeongjun Park
2024-04-20 3:04 ` Jakub Kicinski
2024-04-20 8:21 ` Jeongjun Park
2024-04-22 13:04 ` Dan Carpenter [this message]
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=7d690606-7abe-42db-80d4-2ef979e8303b@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=aha310510@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8e03da5d64bc85098811@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).