From: Jiri Slaby <jirislaby@kernel.org>
To: "D. Starke" <daniel.starke@siemens.com>,
linux-serial@vger.kernel.org, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] tty: n_gsm: fix invalid gsmtty_write_room() result
Date: Mon, 9 May 2022 12:31:54 +0200 [thread overview]
Message-ID: <f55e96d0-6683-0aef-4d4c-5c635e85aabd@kernel.org> (raw)
In-Reply-To: <20220504081733.3494-3-daniel.starke@siemens.com>
On 04. 05. 22, 10:17, D. Starke wrote:
> From: Daniel Starke <daniel.starke@siemens.com>
>
> gsmtty_write() does not prevent the user to use the full fifo size of 4096
> bytes as allocated in gsm_dlci_alloc(). However, gsmtty_write_room() tries
> to limit the return value by 'TX_SIZE' and returns a negative value if the
> fifo has more than 'TX_SIZE' bytes stored. This is obviously wrong as
> 'TX_SIZE' is defined as 512.
> Define 'TX_SIZE' to the fifo size and use it accordingly for allocation to
> keep the current behavior. Return the correct remaining size of the fifo in
> gsmtty_write_room() via kfifo_avail().
Right.
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
> Cc: stable@vger.kernel.org
> Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
> ---
> drivers/tty/n_gsm.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index bcb714031d69..fd8b86dde525 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -137,6 +137,7 @@ struct gsm_dlci {
> int retries;
> /* Uplink tty if active */
> struct tty_port port; /* The tty bound to this DLCI if there is one */
> +#define TX_SIZE 4096 /* Must be power of 2. */
Only that I'd not put the macro definition here. But outside the structure.
> struct kfifo fifo; /* Queue fifo for the DLCI */
> int adaption; /* Adaption layer in use */
> int prev_adaption;
> @@ -1731,7 +1732,7 @@ static struct gsm_dlci *gsm_dlci_alloc(struct gsm_mux *gsm, int addr)
> return NULL;
> spin_lock_init(&dlci->lock);
> mutex_init(&dlci->mutex);
> - if (kfifo_alloc(&dlci->fifo, 4096, GFP_KERNEL) < 0) {
> + if (kfifo_alloc(&dlci->fifo, TX_SIZE, GFP_KERNEL) < 0) {
> kfree(dlci);
> return NULL;
> }
> @@ -2976,8 +2977,6 @@ static struct tty_ldisc_ops tty_ldisc_packet = {
> * Virtual tty side
> */
>
> -#define TX_SIZE 512
> -
> /**
> * gsm_modem_upd_via_data - send modem bits via convergence layer
> * @dlci: channel
> @@ -3217,7 +3216,7 @@ static unsigned int gsmtty_write_room(struct tty_struct *tty)
> struct gsm_dlci *dlci = tty->driver_data;
> if (dlci->state == DLCI_CLOSED)
> return 0;
> - return TX_SIZE - kfifo_len(&dlci->fifo);
> + return kfifo_avail(&dlci->fifo);
> }
>
> static unsigned int gsmtty_chars_in_buffer(struct tty_struct *tty)
--
js
suse labs
next prev parent reply other threads:[~2022-05-09 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 8:17 [PATCH 1/3] tty: n_gsm: fix buffer over-read in gsm_dlci_data() D. Starke
2022-05-04 8:17 ` [PATCH 2/3] tty: n_gsm: fix mux activation issues in gsm_config() D. Starke
2022-05-09 10:28 ` Jiri Slaby
2022-05-04 8:17 ` [PATCH 3/3] tty: n_gsm: fix invalid gsmtty_write_room() result D. Starke
2022-05-09 10:31 ` Jiri Slaby [this message]
2022-05-09 10:41 ` [PATCH 1/3] tty: n_gsm: fix buffer over-read in gsm_dlci_data() Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 11:10 [PATCH 3/3] tty: n_gsm: fix invalid gsmtty_write_room() result Starke, Daniel
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=f55e96d0-6683-0aef-4d4c-5c635e85aabd@kernel.org \
--to=jirislaby@kernel.org \
--cc=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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).