linux-kernel - Re: usb/serial/io_ti.c: inconsequent NULL checking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2c0942db0802191538k79f93ca5p93a1883a449f3bb0@mail.gmail.com>
Date:	Tue, 19 Feb 2008 15:38:58 -0800
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Greg KH" <gregkh@...e.de>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: usb/serial/io_ti.c: inconsequent NULL checking

On Feb 19, 2008 3:25 PM, Greg KH <gregkh@...e.de> wrote:
> On Wed, Feb 20, 2008 at 12:49:15AM +0200, Adrian Bunk wrote:
> > The Coverity checker spotted the following inconsequent NULL checking
> > introduced by commit d5f5bcd425b771c0b7ff5a650b2ce061ac8bbb87:
> >
> > <--  snip  -->
>
> It's not a real problem, that pointer can't go away.

I think he meant inconsistent not "inconsequent."

Either the test of port->tty here is unneeded:

 if (port->tty)
               port->tty->low_latency = low_latency;

...or the lack of test of port->tty here is a mistake:

	 edge_set_termios (port, port->tty->termios);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/