linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@distanz.ch>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-serial@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw
Subject: Re: [smatch stuff] altera_uart: inconsistent checks for null
Date: Tue, 1 Mar 2011 09:10:34 +0100	[thread overview]
Message-ID: <20110301081034.GP14058@distanz.ch> (raw)
In-Reply-To: <20110219140204.GE4384@bicker>

On 2011-02-19 at 15:02:05 +0100, Dan Carpenter <error27@gmail.com> wrote:
> On Sat, Feb 19, 2011 at 02:22:17PM +0100, Tobias Klauser wrote:
> > On 2011-02-19 at 10:31:07 +0100, Dan Carpenter <error27@gmail.com> wrote:
> > > Patch 2780ad42f5fe67 "tty: serial: altera_uart: Use port->regshift to
> > > store bus shift" added a NULL check for platp in altera_uart_probe() but
> > > not consistently through out the function.
> > > 
> > > drivers/tty/serial/altera_uart.c +553 altera_uart_probe(43)
> > > 	error: we previously assumed 'platp' could be null.
> > > 
> > >    545          if (platp)
> > >                    ^^^^^^^
> > > checked here.
> > > 
> > >    546                  port->regshift = platp->bus_shift;
> > >    547          else
> > >    548                  port->regshift = 0;
> > >    549
> > >    550          port->line = i;
> > >    551          port->type = PORT_ALTERA_UART;
> > >    552          port->iotype = SERIAL_IO_MEM;
> > >    553          port->uartclk = platp->uartclk;
> > >                                 ^^^^^^^
> > > potential NULL dereference?
> > 
> > Not at the moment, because everybody is using platform data at the
> > momenti, so platp should never be NULL. Still this is inconsistent and
> > shouldn't be there like this. The dereference on line 553 will go away
> > with the patch introducing device tree support to altera_uart [1].
> > 
> > [1] https://lkml.org/lkml/2011/2/18/100
> > 
> > >    554          port->ops = &altera_uart_ops;
> > > 
> > > I don't know the right way to address this.
> > 
> > I guess either Greg or Grant will take the above mentioned patch (it
> > depends on a commit in Grant's tree).

Grant has taken the patch into his tree and it is now in linux-next.
I ran smatch against it and the error went away.

Cheers
Tobias

      reply	other threads:[~2011-03-01  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  9:31 [smatch stuff] altera_uart: inconsistent checks for null Dan Carpenter
2011-02-19 13:22 ` Tobias Klauser
2011-02-19 14:02   ` Dan Carpenter
2011-03-01  8:10     ` Tobias Klauser [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=20110301081034.GP14058@distanz.ch \
    --to=tklauser@distanz.ch \
    --cc=error27@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=nios2-dev@sopc.et.ntust.edu.tw \
    /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).