From: Greg KH <gregkh@linuxfoundation.org>
To: Tom Rix <trix@redhat.com>
Cc: jirislaby@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
peter@hurleysoftware.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] serial: core: check if uart_get_info succeeds before using
Date: Tue, 7 Jun 2022 15:11:11 +0200 [thread overview]
Message-ID: <Yp9Ob3pXUS8Jggm4@kroah.com> (raw)
In-Reply-To: <20220529134605.12881-1-trix@redhat.com>
On Sun, May 29, 2022 at 09:46:05AM -0400, Tom Rix wrote:
> clang static analysis reports this representative issue
> drivers/tty/serial/serial_core.c:2818:9: warning: 3rd function call argument is an uninitialized value [core.CallAndMessage]
> return sprintf(buf, "%d\n", tmp.iomem_reg_shift);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> uart_get_info() is used the *show() functions. When uart_get_info() fails, what is reported
> is garbage. So check if uart_get_info() succeeded.
>
> Fixes: 4047b37122d1 ("serial: core: Prevent unsafe uart port access, part 1")
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/tty/serial/serial_core.c | 52 ++++++++++++++++++++++++--------
> 1 file changed, 39 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index 9a85b41caa0a..4160f6711c5d 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -2690,7 +2690,9 @@ static ssize_t uartclk_show(struct device *dev,
> struct serial_struct tmp;
> struct tty_port *port = dev_get_drvdata(dev);
>
> - uart_get_info(port, &tmp);
> + if (uart_get_info(port, &tmp))
> + return 0;
As Andy pointed out, this is an error, don't tell userspace that all
went well and yet you returned no data? That will just confuse it.
thanks,
greg k-h
prev parent reply other threads:[~2022-06-07 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 13:46 [PATCH] serial: core: check if uart_get_info succeeds before using Tom Rix
2022-06-06 18:29 ` Nick Desaulniers
2022-06-07 10:15 ` Andy Shevchenko
2022-06-07 13:11 ` Greg KH [this message]
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=Yp9Ob3pXUS8Jggm4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peter@hurleysoftware.com \
--cc=trix@redhat.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.