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
Subject: Re: [PATCH v3] serial: imx: Suppress false positive sysrq lockdep warning
Date: Fri, 01 Oct 2021 23:15:33 -0300 [thread overview]
Message-ID: <0bbe2832eb2dc3a7c32f3d484ab42208@denx.de> (raw)
In-Reply-To: <YVcTluYb6XOiOXZn@hovoldconsulting.com>
On 01/10/2021 10:56, Johan Hovold wrote:
> No, no, no.
>
> Just replace this unlock with uart_unlock_and_check_sysrq() and do the
> corresponding change in imx_uart_int(). The result is an even smaller
> diff than what you're currently proposing and without any performance
> penalty from dropping and reacquiring the lock.
Just to be clear, this is something that I have also tried:
diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
index 8b121cd869e9..b652908f0bf1 100644
--- a/drivers/tty/serial/imx.c
+++ b/drivers/tty/serial/imx.c
@@ -803,7 +803,7 @@ static irqreturn_t __imx_uart_rxint(int irq, void
*dev_id)
continue;
}
- if (uart_handle_sysrq_char(&sport->port, (unsigned char)rx))
+ if (uart_prepare_sysrq_char(&sport->port, (unsigned char)rx))
continue;
if (unlikely(rx & URXD_ERR)) {
@@ -858,7 +858,7 @@ static irqreturn_t imx_uart_rxint(int irq, void
*dev_id)
ret = __imx_uart_rxint(irq, dev_id);
- spin_unlock(&sport->port.lock);
+ uart_unlock_and_check_sysrq(&sport->port);
return ret;
}
@@ -991,7 +991,7 @@ static irqreturn_t imx_uart_int(int irq, void
*dev_id)
ret = IRQ_HANDLED;
}
- spin_unlock(&sport->port.lock);
+ uart_unlock_and_check_sysrq(&sport->port);
return ret;
}
@@ -1977,9 +1977,7 @@ imx_uart_console_write(struct console *co, const
char *s, unsigned int count)
unsigned int ucr1;
int locked = 1;
- if (sport->port.sysrq)
- locked = 0;
- else if (oops_in_progress)
+ if (oops_in_progress)
locked = spin_trylock_irqsave(&sport->port.lock, flags);
else
spin_lock_irqsave(&sport->port.lock, flags);
, but still get the lockdep warning in this case.
Thanks
next prev parent reply other threads:[~2021-10-02 2:15 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 [this message]
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 ` [PATCH v3] serial: imx: Suppress false positive sysrq lockdep warning Fabio Estevam
2021-10-06 12:02 ` 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=0bbe2832eb2dc3a7c32f3d484ab42208@denx.de \
--to=festevam@denx.de \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marex@denx.de \
--cc=michael@walle.cc \
--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).