diff options
| author | Jiri Slaby <jslaby@suse.cz> | 2022-03-08 14:51:53 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-03-18 15:13:36 +0300 |
| commit | 988c7c00691008ea1daaa1235680a0da49dab4e8 (patch) | |
| tree | e81ae27f0f13bf912d670c462dc3e09e989530f5 /scripts/gdb/linux/proc.py | |
| parent | 4f6f194f2be43c1df9ad031de86cdaffa5c8084d (diff) | |
| download | linux-988c7c00691008ea1daaa1235680a0da49dab4e8.tar.xz | |
serial: samsung_tty: do not unlock port->lock for uart_write_wakeup()
The commit c15c3747ee32 (serial: samsung: fix potential soft lockup
during uart write) added an unlock of port->lock before
uart_write_wakeup() and a lock after it. It was always problematic to
write data from tty_ldisc_ops::write_wakeup and it was even documented
that way. We fixed the line disciplines to conform to this recently.
So if there is still a missed one, we should fix them instead of this
workaround.
On the top of that, s3c24xx_serial_tx_dma_complete() in this driver
still holds the port->lock while calling uart_write_wakeup().
So revert the wrap added by the commit above.
Cc: Thomas Abraham <thomas.abraham@linaro.org>
Cc: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Hyeonkook Kim <hk619.kim@samsung.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Link: https://lore.kernel.org/r/20220308115153.4225-1-jslaby@suse.cz
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions