All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sherry Sun <sherry.sun@nxp.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "jirislaby@kernel.org" <jirislaby@kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH 1/2] tty: serial: fsl_lpuart: fix the potential bug of division or modulo by zero
Date: Mon, 26 Apr 2021 11:51:39 +0000	[thread overview]
Message-ID: <AM0PR04MB49470E50CFAB8C36EABB241192429@AM0PR04MB4947.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <YIalMRdbAKZpIJWP@kroah.com>

Hi Greg,

> > > >  drivers/tty/serial/fsl_lpuart.c | 3 +++
> > > >  1 file changed, 3 insertions(+)
> > > >
> > > > diff --git a/drivers/tty/serial/fsl_lpuart.c
> > > > b/drivers/tty/serial/fsl_lpuart.c index 794035041744..777d54b593f8
> > > > 100644
> > > > --- a/drivers/tty/serial/fsl_lpuart.c
> > > > +++ b/drivers/tty/serial/fsl_lpuart.c
> > > > @@ -2414,6 +2414,9 @@ lpuart32_console_get_options(struct
> > > > lpuart_port *sport, int *baud,
> > > >
> > > >  	bd = lpuart32_read(&sport->port, UARTBAUD);
> > > >  	bd &= UARTBAUD_SBR_MASK;
> > > > +	if (!bd)
> > > > +		return;
> > >
> > > How can this ever happen?
> > >
> > > Not to say this is a bad check, but it feels like this can't really
> > > happen in real life, what code patch could create this result?
> > >
> > > And have you tested this on real hardware?
> > >
> >
> > Thanks for the reviewing, yes, I have tested the patchset on the real
> hardware.
> >
> > Seems the coverity check is static scan, so cannot judge if UARTBAUD
> Register will be zero.
> > I just found below statement in the uart reference manual: "When SBR is 1
> - 8191, the baud rate equals "baud clock / ((OSR+1) × SBR)"."
> > Since I am not familiar with uart, do you mean that the value of UARTBAUD
> Register will never be zero, so this case will not happen in real word?
> 
> Given that this never has happened with hardware for such an old device,
> perhaps it is impossible.  But it would be good to check.
> 
> > If yes, I will drop this patch.
> 
> Handling "bad data" from hardware is never a bad idea, so I don't
> necessarily want to drop this patch, I just want to try to figure out if this is a
> "incase the hardware is broken/malicious" type of change, vs.
> a "this bug we are seeing in real hardware" type of change.
> 

Yes, you are right, the probability of hardware happen in this case is really low. But we cannot guarantee that it will never happen.
So will this check here be accepted? Thanks!

Best regards
Sherry

> thanks,
> 
> greg k-h

  reply	other threads:[~2021-04-26 11:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  7:49 [PATCH 0/2] Fix two coverity issues in fsl_lpuart.c Sherry Sun
2021-04-26  7:49 ` [PATCH 1/2] tty: serial: fsl_lpuart: fix the potential bug of division or modulo by zero Sherry Sun
2021-04-26  8:08   ` Greg KH
2021-04-26 11:30     ` Sherry Sun
2021-04-26 11:34       ` Greg KH
2021-04-26 11:51         ` Sherry Sun [this message]
2021-04-26 12:23           ` Greg KH
2021-04-26 12:50             ` Sherry Sun
2021-04-26  7:49 ` [PATCH 2/2] tty: serial: fsl_lpuart: fix the potential bug of dereference null return value Sherry Sun
2021-04-26  8:09   ` Greg KH
2021-04-26 11:39     ` Sherry Sun
2021-04-26 11:57       ` Fabio Estevam
2021-04-26 12:09         ` Sherry Sun
2021-04-26 12:15           ` Fabio Estevam
2021-04-26 12:48             ` Sherry Sun
2021-04-26 12:22       ` Greg KH
2021-04-26 12:46         ` Sherry Sun

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=AM0PR04MB49470E50CFAB8C36EABB241192429@AM0PR04MB4947.eurprd04.prod.outlook.com \
    --to=sherry.sun@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-imx@nxp.com \
    --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 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.