From: syzbot <syzbot+8e03da5d64bc85098811@syzkaller.appspotmail.com>
To: aha310510@gmail.com
Cc: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] possible deadlock in serial8250_console_write
Date: Fri, 19 Apr 2024 23:09:24 -0700 [thread overview]
Message-ID: <000000000000cd73500616810b77@google.com> (raw)
In-Reply-To: <20240420060919.62280-1-aha310510@gmail.com>
> please test deadlock in serial8250_console_write
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
This crash does not have a reproducer. I cannot test it.
>
> ---
> drivers/net/ppp/ppp_async.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ppp/ppp_async.c b/drivers/net/ppp/ppp_async.c
> index c33c3db3cc08..d12b8155e839 100644
> --- a/drivers/net/ppp/ppp_async.c
> +++ b/drivers/net/ppp/ppp_async.c
> @@ -134,11 +134,11 @@ static struct asyncppp *ap_get(struct tty_struct *tty)
> {
> struct asyncppp *ap;
>
> - read_lock(&disc_data_lock);
> + read_lock_irq(&disc_data_lock);
> ap = tty->disc_data;
> if (ap != NULL)
> refcount_inc(&ap->refcnt);
> - read_unlock(&disc_data_lock);
> + read_unlock_irq(&disc_data_lock);
> return ap;
> }
>
> --
> 2.34.1
prev parent reply other threads:[~2024-04-20 6:09 UTC|newest]
Thread overview: 8+ 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
2024-04-20 6:09 ` [syzbot] [hams?] possible deadlock in serial8250_console_write Jeongjun Park
2024-04-20 6:09 ` syzbot [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=000000000000cd73500616810b77@google.com \
--to=syzbot+8e03da5d64bc85098811@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.