From: Hugo Villeneuve <hugo@hugovil.com>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
ilpo.jarvinen@linux.intel.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, l.sanfilippo@kunbus.com,
lukas@wunner.de, p.rosenberger@kunbus.com,
stable@vger.kernel.org
Subject: Re: [PATCH 5/6] serial: core: make sure RS485 is cannot be enabled when it is not supported
Date: Fri, 29 Sep 2023 08:17:12 -0400 [thread overview]
Message-ID: <20230929081712.7824dca40828ff873b3352ff@hugovil.com> (raw)
In-Reply-To: <20230928221246.13689-6-LinoSanfilippo@gmx.de>
Hi,
remove superfluous "is" after RS485 in patch title.
Hugo.
On Fri, 29 Sep 2023 00:12:45 +0200
Lino Sanfilippo <LinoSanfilippo@gmx.de> wrote:
> From: Lino Sanfilippo <l.sanfilippo@kunbus.com>
>
> Some uart drivers specify a rs485_config() function and then decide later
> to disable RS485 support for some reason (e.g. imx and ar933).
>
> In these cases userspace may be able to activate RS485 via TIOCSRS485
> nevertheless, since in uart_set_rs485_config() an existing rs485_config()
> function indicates that RS485 is supported.
>
> Make sure that this is not longer possible by checking the uarts
> rs485_supported.flags instead and bailing out if SER_RS485_ENABLED is not
> set.
>
> Furthermore instead of returning an empty structure return -ENOTTY if the
> RS485 configuration is requested via TIOCGRS485 but RS485 is not supported.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Lino Sanfilippo <l.sanfilippo@kunbus.com>
> ---
> drivers/tty/serial/serial_core.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index f4feebf8200f..dca09877fabc 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -1432,6 +1432,9 @@ static int uart_get_rs485_config(struct uart_port *port,
> unsigned long flags;
> struct serial_rs485 aux;
>
> + if (!(port->rs485_supported.flags & SER_RS485_ENABLED))
> + return -ENOTTY;
> +
> spin_lock_irqsave(&port->lock, flags);
> aux = port->rs485;
> spin_unlock_irqrestore(&port->lock, flags);
> @@ -1449,7 +1452,7 @@ static int uart_set_rs485_config(struct tty_struct *tty, struct uart_port *port,
> int ret;
> unsigned long flags;
>
> - if (!port->rs485_config)
> + if (!(port->rs485_supported.flags & SER_RS485_ENABLED))
> return -ENOTTY;
>
> if (copy_from_user(&rs485, rs485_user, sizeof(*rs485_user)))
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-09-29 12:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 22:12 [PATCH 0/6] Fixes and improvements for RS485 Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 1/6] serial: Do not hold the port lock when setting rx-during-tx GPIO Lino Sanfilippo
2023-09-29 5:50 ` Greg KH
2023-09-29 12:21 ` Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 2/6] serial: amba-pl011: get rid of useless wrapper pl011_get_rs485_mode() Lino Sanfilippo
2023-09-28 22:33 ` Lukas Wunner
2023-09-28 22:12 ` [PATCH 3/6] serial: core: set missing supported flag for RX during TX GPIO Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 4/6] serial: core: fix sanitizing check for RTS settings Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 5/6] serial: core: make sure RS485 is cannot be enabled when it is not supported Lino Sanfilippo
2023-09-29 12:17 ` Hugo Villeneuve [this message]
2023-09-29 12:25 ` Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 6/6] serial: imx: do not set RS485 enabled if " Lino Sanfilippo
2023-09-29 5:51 ` Greg KH
2023-09-29 12:22 ` Lino Sanfilippo
2023-09-29 6:39 ` Uwe Kleine-König
2023-09-29 13:46 ` Lino Sanfilippo
2023-09-29 15:44 ` Uwe Kleine-König
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=20230929081712.7824dca40828ff873b3352ff@hugovil.com \
--to=hugo@hugovil.com \
--cc=LinoSanfilippo@gmx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.rosenberger@kunbus.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®