From: Fabio Estevam <festevam@denx.de>
To: Johan Hovold <johan@kernel.org>
Cc: gregkh@linuxfoundation.org, michael@walle.cc,
linux-serial@vger.kernel.org, marex@denx.de,
u.kleine-koenig@pengutronix.de, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] serial: imx: Suppress false positive sysrq lockdep warning
Date: Wed, 06 Oct 2021 07:52:25 -0300 [thread overview]
Message-ID: <c774fe18362b4cc19111078f2cd9ae82@denx.de> (raw)
In-Reply-To: <YV1Z8JslFiBSFGJF@hovoldconsulting.com>
Hi Johan,
On 06/10/2021 05:10, Johan Hovold wrote:
> Ok, thanks for testing. The above is what I meant and it does fix the
> false-positive lockdep splat which motivated
> uart_unlock_and_check_sysrq() to be added in the first place.
>
> Looking closer at the splat you reported (which you've edited quite
> heavily), it becomes apparent that you are now hitting a different
> locking issue. And it's not a false positive this time.
>
> There a problem with the workqueue debugging code, which unless fixed
> at
> the source, would prevent any console driver from queueing work while
> holding a lock also taken in their write paths. And
> tty_flip_buffer_push() is just one example of many.
>
> I can easily reproduce the splat with another serial driver, and I've
> also been able to trigger the actual deadlock.
>
> I've prepared a patch that takes care of the workqueue state dumping,
> which I'll send as a reply to this mail. Would you mind giving it a
> spin
> with the imx driver as well?
Yes, after applying only your patch I no longer get the lockdep
splat. I have replied with my Tested-by, thanks.
next prev parent reply other threads:[~2021-10-06 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 10:18 [PATCH v3] serial: imx: Suppress false positive sysrq lockdep warning Fabio Estevam
2021-10-01 13:56 ` Johan Hovold
2021-10-01 14:48 ` Fabio Estevam
2021-10-02 2:15 ` Fabio Estevam
2021-10-06 8:10 ` Johan Hovold
2021-10-06 8:11 ` [PATCH] workqueue: fix state-dump console deadlock Johan Hovold
2021-10-06 9:19 ` Petr Mladek
2021-10-06 10:07 ` Johan Hovold
2021-10-06 10:49 ` Fabio Estevam
2021-10-06 10:52 ` Fabio Estevam [this message]
2021-10-06 12:02 ` [PATCH v3] serial: imx: Suppress false positive sysrq lockdep warning Johan Hovold
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=c774fe18362b4cc19111078f2cd9ae82@denx.de \
--to=festevam@denx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=johan@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marex@denx.de \
--cc=michael@walle.cc \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tj@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 NNTP newsgroup(s).