From: Greg KH <gregkh@linuxfoundation.org>
To: Anthony Mallet <anthony.mallet@laas.fr>
Cc: Oliver Neukum <oneukum@suse.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 2/2] USB: cdc-acm: fix rounding error in TIOCSSERIAL
Date: Thu, 12 Mar 2020 09:38:27 +0100 [thread overview]
Message-ID: <20200312083827.GA102663@kroah.com> (raw)
In-Reply-To: <20200310101027.32152-2-anthony.mallet@laas.fr>
On Tue, Mar 10, 2020 at 11:10:27AM +0100, Anthony Mallet wrote:
> Quoting the bug reporter:
>
> By default, tty_port_init() initializes those parameters to a multiple
> of HZ. For instance in line 69 of tty_port.c:
> port->close_delay = (50 * HZ) / 100;
> https://github.com/torvalds/linux/blob/master/drivers/tty/tty_port.c#L69
>
> With e.g. CONFIG_HZ = 250 (as this is the case for Ubuntu 18.04
> linux-image-4.15.0-37-generic), the default setting for close_delay is
> thus 125.
>
> When ioctl(fd, TIOCGSERIAL, &s) is executed, the setting returned in
> user space is '12' (125/10). When ioctl(fd, TIOCSSERIAL, &s) is then
> executed with the same setting '12', the value is interpreted as '120'
> which is different from the current setting and a EPERM error may be
> raised by set_serial_info() if !CAP_SYS_ADMIN.
> https://github.com/torvalds/linux/blob/master/drivers/usb/class/cdc-acm.c#L919
>
> Fixes: ba2d8ce9db0a6 ("cdc-acm: implement TIOCSSERIAL to avoid blocking close(2)")
> Signed-off-by: Anthony Mallet <anthony.mallet@laas.fr>
> Cc: stable <stable@vger.kernel.org>
> ---
> Changed in v2: fix typo (extra closing brace)
> Changed in v3: version this patch series
> ---
> drivers/usb/class/cdc-acm.c | 27 +++++++++++++++++----------
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
> index da619176deca..a41a3d27016c 100644
> --- a/drivers/usb/class/cdc-acm.c
> +++ b/drivers/usb/class/cdc-acm.c
> @@ -907,6 +907,7 @@ static int set_serial_info(struct tty_struct *tty, struct serial_struct *ss)
> {
> struct acm *acm = tty->driver_data;
> unsigned int closing_wait, close_delay;
> + unsigned int old_closing_wait, old_close_delay;
> int retval = 0;
>
> close_delay = msecs_to_jiffies(ss->close_delay * 10);
> @@ -914,19 +915,24 @@ static int set_serial_info(struct tty_struct *tty, struct serial_struct *ss)
> ASYNC_CLOSING_WAIT_NONE :
> msecs_to_jiffies(ss->closing_wait * 10);
>
> + /* we must redo the rounding here, so that the values match */
> + old_close_delay = jiffies_to_msecs(acm->port.close_delay) / 10;
> + old_closing_wait = acm->port.closing_wait == ASYNC_CLOSING_WAIT_NONE ?
> + ASYNC_CLOSING_WAIT_NONE :
> + jiffies_to_msecs(acm->port.closing_wait) / 10;
> +
> mutex_lock(&acm->port.mutex);
>
> - if (!capable(CAP_SYS_ADMIN)) {
> - if ((close_delay != acm->port.close_delay) ||
> - (closing_wait != acm->port.closing_wait))
> + if ((ss->close_delay != old_close_delay) ||
> + (ss->closing_wait != old_closing_wait)) {
> + if (!capable(CAP_SYS_ADMIN))
> retval = -EPERM;
> - else
> - retval = -EOPNOTSUPP;
> - } else {
> - acm->port.close_delay = close_delay;
> - acm->port.closing_wait = closing_wait;
> - }
> + else {
> + acm->port.close_delay = close_delay;
> + acm->port.closing_wait = closing_wait;
> + }
> + } else
> + retval = -EOPNOTSUPP;
>
> mutex_unlock(&acm->port.mutex);
> return retval;
> --
> 2.17.1
>
This patch doesn't apply to my usb-linus branch at all. What
tree/branch did you make it against?
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-12 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 10:10 [PATCH v3 1/2] USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL Anthony Mallet
2020-03-10 10:10 ` [PATCH v3 2/2] USB: cdc-acm: fix rounding error " Anthony Mallet
2020-03-12 8:38 ` Greg KH [this message]
2020-03-12 9:15 ` Anthony Mallet
2020-03-12 9:35 ` Greg KH
2020-03-12 13:30 ` Anthony Mallet
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=20200312083827.GA102663@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anthony.mallet@laas.fr \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.