mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Naranjo Manuel Francisco <naranjo.manuel@gmail.com>
To: <bunk@stusta.de>
Cc: gregkh@suse.de, linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: drivers/usb/serial/aircable.c: inconsequent NULL checking
Date: Wed, 15 Nov 2006 15:14:27 -0300	[thread overview]
Message-ID: <20061115151427.47ffdd75@manuel> (raw)
In-Reply-To: <360bc8300611151008v44e12cebx65688233fc614906@mail.gmail.com>

> 2006/11/11, Adrian Bunk <bunk@stusta.de>:
> > The Coverity checker spotted the following in
> > drivers/usb/serial/aircable.c:
> >
> > <--  snip  -->
> >
> > ...
> > static void aircable_read(void *params)
> > {
> > ...


Hi everyone,
Sorry for the long time response but here is the patch, I think this way should work, if anyone has any suggestion let me know. What I do now is, in case I don't have the tty available I reschedule the work, I have tried it and it works with no problem, I even tried removing the device, and didn't find anything strange.

Manuel Naranjo

Signed-off-by: Naranjo Manuel <naranjo.manuel@gmail.com>

----

--- linux2/drivers/usb/serial/aircable.c.orig	2006-11-15 15:03:40.000000000 -0300
+++ linux2/drivers/usb/serial/aircable.c	2006-11-12 21:59:05.000000000 -0300
@@ -270,8 +270,11 @@ static void aircable_read(void *params)
 	 */
 	tty = port->tty;
 
-	if (!tty)
+	if (!tty){
 		schedule_work(&priv->rx_work);
+		err("%s - No tty available", __FUNCTION__);
+		return ;
+	}
 
 	count = min(64, serial_buf_data_avail(priv->rx_buf));
 


      parent reply	other threads:[~2006-11-15 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 16:13 Adrian Bunk
     [not found] ` <360bc8300611151008v44e12cebx65688233fc614906@mail.gmail.com>
2006-11-15 18:14   ` Naranjo Manuel Francisco [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=20061115151427.47ffdd75@manuel \
    --to=naranjo.manuel@gmail.com \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

Powered by JetHome