mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@gmx.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] missing NULL check in drivers/char/n_tty.c
Date: Mon, 21 Jun 2004 11:24:30 +0300	[thread overview]
Message-ID: <20040621082430.GA11566@callisto.yi.org> (raw)
In-Reply-To: <20040621003944.48f4b4be.akpm@osdl.org>

On Mon, Jun 21, 2004 at 12:39:44AM -0700, Andrew Morton wrote:
> Dan Aloni <da-x@gmx.net> wrote:
> >
> > On Sun, Jun 20, 2004 at 11:58:24PM -0700, Andrew Morton wrote:
> > > Dan Aloni <da-x@gmx.net> wrote:
> > > >
> > > > The rest of the kernel treats tty->driver->chars_in_buffer as a possible
> > > >  NULL. This patch changes normal_poll() to be consistent with the rest of
> > > >  the code.
> > > 
> > > It would be better to change the rest of the kernel - remove the tests.
> > > 
> > > If any driver fails to implement ->chars_in_buffer() then we get a nice
> > > oops which tells us that driver needs a stub handler.
> > 
> > Are you sure that it won't affect the logic in tty_wait_until_sent() 
> > drastically? It acts quite differently when ->chars_in_buffer == NULL.
> 
> I did a quick grep and it appears that all drivers have set ->chars_in_buffer().
> 
> I suspect there are no drivers which fail to set chars_in_buffer. 
> Otherwise normal_poll() would have been oopsing in 2.4, 2.5 and 2.6?

Right. Perhaps this should be applied:

Signed-off-by: Dan Aloni <da-x@colinux.org>

--- linux-2.6.7/drivers/char/n_hdlc.c
+++ linux-2.6.7/drivers/char/n_hdlc.c
@@ -760,8 +760,7 @@
 
 	case TIOCOUTQ:
 		/* get the pending tx byte count in the driver */
-		count = tty->driver->chars_in_buffer ?
-				tty->driver->chars_in_buffer(tty) : 0;
+		count = tty->driver->chars_in_buffer(tty);
 		/* add size of next output frame in queue */
 		spin_lock_irqsave(&n_hdlc->tx_buf_list.spinlock,flags);
 		if (n_hdlc->tx_buf_list.head)
--- linux-2.6.7/drivers/char/tty_ioctl.c
+++ linux-2.6.7/drivers/char/tty_ioctl.c
@@ -45,8 +45,6 @@
 	
 	printk(KERN_DEBUG "%s wait until sent...\n", tty_name(tty, buf));
 #endif
-	if (!tty->driver->chars_in_buffer)
-		return;
 	add_wait_queue(&tty->write_wait, &wait);
 	if (!timeout)
 		timeout = MAX_SCHEDULE_TIMEOUT;
@@ -461,8 +459,7 @@
 			}
 			return 0;
 		case TIOCOUTQ:
-			return put_user(tty->driver->chars_in_buffer ?
-					tty->driver->chars_in_buffer(tty) : 0,
+			return put_user(tty->driver->chars_in_buffer(tty),
 					(int __user *) arg);
 		case TIOCINQ:
 			retval = tty->read_cnt;

-- 
Dan Aloni
da-x@colinux.org

  reply	other threads:[~2004-06-21  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  6:38 Dan Aloni
2004-06-21  6:58 ` Andrew Morton
2004-06-21  7:36   ` Dan Aloni
2004-06-21  7:39     ` Andrew Morton
2004-06-21  8:24       ` Dan Aloni [this message]
2004-06-21 15:06         ` Paul Fulghum
2004-06-21 18:46           ` Andrew Morton
2004-06-21 19:52             ` Paul Fulghum
2004-06-21 22:48             ` Dan Aloni
2004-06-21 23:56               ` Paul Fulghum

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=20040621082430.GA11566@callisto.yi.org \
    --to=da-x@gmx.net \
    --cc=akpm@osdl.org \
    --cc=da-x@colinux.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®