From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "yiyang (D)" <yiyang13@huawei.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
hedonistsmith@gmail.com, daniel.starke@siemens.com,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: BUG: sleeping function called from invalid context in console_lock
Date: Mon, 18 Sep 2023 17:19:54 +0200 [thread overview]
Message-ID: <2023091838-shrubs-paragraph-e579@gregkh> (raw)
In-Reply-To: <c1dbec59-9564-5705-1ae6-200860a7371b@huawei.com>
On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
> In recent years, this problem has been reported in syzkaller all the time.
>
> Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
>
> Historically, the developers have tried to fix this problem by use mutex
> instead spinlock, but it didn't solve the problem..
>
> Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
>
> Other developers have recently reported this problem, but no one has
> continued to try to fix it.
>
> Link:
> https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
>
> Anyway, do we have any ideas for solving this problem?
Nope! Why do you think this is something that even needs to be
addressed?
next prev parent reply other threads:[~2023-09-18 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42c2c0c4-9ee2-6426-8c3c-2585e0345fcb@huawei.com>
2023-09-18 13:35 ` BUG: sleeping function called from invalid context in console_lock yiyang (D)
2023-09-18 15:19 ` Greg Kroah-Hartman [this message]
2023-09-27 7:48 ` yiyang (D)
2023-09-27 8:24 ` Greg Kroah-Hartman
2023-09-27 9:15 ` yiyang (D)
2023-09-27 9:41 ` Greg Kroah-Hartman
2020-05-18 1:22 syzbot
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=2023091838-shrubs-paragraph-e579@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=daniel.starke@siemens.com \
--cc=hedonistsmith@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=yiyang13@huawei.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.