USB: class: CDC-ACM: fix race between get_serial and set_serial
commit b41c1fa155ba56d125885b0191aabaf3c508d0a3 upstream.
TIOCGSERIAL is an ioctl. Thus it must be atomic. It returns
two values. Racing with set_serial it can return an inconsistent
result. The mutex must be taken.
In terms of logic the bug is as old as the driver. In terms of
code it goes back to the conversion to the get_serial and
set_serial methods.
Signed-off-by: Oliver Neukum <oneukum@suse.com>
Cc: stable <stable@kernel.org>
Fixes: 99f75a1fcd ("cdc-acm: switch to ->[sg]et_serial()")
Link: https://lore.kernel.org/r/20240912141916.1044393-1-oneukum@suse.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
34f0773c94
commit
560ae2252f
1 changed files with 2 additions and 0 deletions
|
|
@ -938,10 +938,12 @@ static int get_serial_info(struct tty_struct *tty, struct serial_struct *ss)
|
||||||
struct acm *acm = tty->driver_data;
|
struct acm *acm = tty->driver_data;
|
||||||
|
|
||||||
ss->line = acm->minor;
|
ss->line = acm->minor;
|
||||||
|
mutex_lock(&acm->port.mutex);
|
||||||
ss->close_delay = jiffies_to_msecs(acm->port.close_delay) / 10;
|
ss->close_delay = jiffies_to_msecs(acm->port.close_delay) / 10;
|
||||||
ss->closing_wait = acm->port.closing_wait == ASYNC_CLOSING_WAIT_NONE ?
|
ss->closing_wait = acm->port.closing_wait == ASYNC_CLOSING_WAIT_NONE ?
|
||||||
ASYNC_CLOSING_WAIT_NONE :
|
ASYNC_CLOSING_WAIT_NONE :
|
||||||
jiffies_to_msecs(acm->port.closing_wait) / 10;
|
jiffies_to_msecs(acm->port.closing_wait) / 10;
|
||||||
|
mutex_unlock(&acm->port.mutex);
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue