summaryrefslogtreecommitdiffstats
path: root/drivers/hwmon/ds620.c
diff options
context:
space:
mode:
authorNguyen Dinh Phi <phind.uet@gmail.com>2021-08-23 02:06:41 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-08-26 14:51:38 +0200
commitbb2853a6a421a052268eee00fd5d3f6b3504b2b1 (patch)
tree4d85d35bb4f84942eec19f5d22757f10c14846f3 /drivers/hwmon/ds620.c
parentserial: vt8500: Use of_device_get_match_data (diff)
downloadlinux-bb2853a6a421a052268eee00fd5d3f6b3504b2b1.tar.xz
linux-bb2853a6a421a052268eee00fd5d3f6b3504b2b1.zip
tty: Fix data race between tiocsti() and flush_to_ldisc()
The ops->receive_buf() may be accessed concurrently from these two functions. If the driver flushes data to the line discipline receive_buf() method while tiocsti() is waiting for the ops->receive_buf() to finish its work, the data race will happen. For example: tty_ioctl |tty_ldisc_receive_buf ->tioctsi | ->tty_port_default_receive_buf | ->tty_ldisc_receive_buf ->hci_uart_tty_receive | ->hci_uart_tty_receive ->h4_recv | ->h4_recv In this case, the h4 receive buffer will be overwritten by the latecomer, and we will lost the data. Hence, change tioctsi() function to use the exclusive lock interface from tty_buffer to avoid the data race. Reported-by: syzbot+97388eb9d31b997fe1d0@syzkaller.appspotmail.com Reviewed-by: Jiri Slaby <jirislaby@kernel.org> Signed-off-by: Nguyen Dinh Phi <phind.uet@gmail.com> Link: https://lore.kernel.org/r/20210823000641.2082292-1-phind.uet@gmail.com Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/hwmon/ds620.c')
0 files changed, 0 insertions, 0 deletions