netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, tilman@imap.cc, greg@kroah.com
Subject: Re: [patch for 2.6.31? 2/2] gigaset: really fix chars_in_buffer
Date: Thu, 06 Aug 2009 20:22:27 -0700 (PDT)	[thread overview]
Message-ID: <20090806.202227.224933454.davem@davemloft.net> (raw)
In-Reply-To: <200908062219.n76MJXhY024495@imap1.linux-foundation.org>

From: akpm@linux-foundation.org
Date: Thu, 06 Aug 2009 15:19:32 -0700

> From: Tilman Schmidt <tilman@imap.cc>
> 
> The tty_operation chars_in_buffer() is not allowed to return a negative
> value to signal an error.  Corrects the problem flagged by commit
> 23198fda7182969b619613a555f8645fdc3dc334, "tty: fix chars_in_buffers".
> 
> Signed-off-by: Tilman Schmidt <tilman@imap.cc>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

I was letting Alan Cox handle changes in this area since it's
TTY stuff, and thus it probably should go to the new TTY
mad man, CC:'d :-)

> ---
> 
>  drivers/isdn/gigaset/interface.c |   19 +++++++------------
>  1 file changed, 7 insertions(+), 12 deletions(-)
> 
> diff -puN drivers/isdn/gigaset/interface.c~gigaset-really-fix-chars_in_buffer drivers/isdn/gigaset/interface.c
> --- a/drivers/isdn/gigaset/interface.c~gigaset-really-fix-chars_in_buffer
> +++ a/drivers/isdn/gigaset/interface.c
> @@ -408,33 +408,28 @@ static int if_write_room(struct tty_stru
>  	return retval;
>  }
>  
> -/* FIXME: This function does not have error returns */
> -
>  static int if_chars_in_buffer(struct tty_struct *tty)
>  {
>  	struct cardstate *cs;
> -	int retval = -ENODEV;
> +	int retval = 0;
>  
>  	cs = (struct cardstate *) tty->driver_data;
>  	if (!cs) {
>  		pr_err("%s: no cardstate\n", __func__);
> -		return -ENODEV;
> +		return 0;
>  	}
>  
>  	gig_dbg(DEBUG_IF, "%u: %s()", cs->minor_index, __func__);
>  
> -	if (mutex_lock_interruptible(&cs->mutex))
> -		return -ERESTARTSYS; // FIXME -EINTR?
> +	mutex_lock(&cs->mutex);
>  
> -	if (!cs->connected) {
> +	if (!cs->connected)
>  		gig_dbg(DEBUG_IF, "not connected");
> -		retval = -ENODEV;
> -	} else if (!cs->open_count)
> +	else if (!cs->open_count)
>  		dev_warn(cs->dev, "%s: device not opened\n", __func__);
> -	else if (cs->mstate != MS_LOCKED) {
> +	else if (cs->mstate != MS_LOCKED)
>  		dev_warn(cs->dev, "can't write to unlocked device\n");
> -		retval = -EBUSY;
> -	} else
> +	else
>  		retval = cs->ops->chars_in_buffer(cs);
>  
>  	mutex_unlock(&cs->mutex);
> _

  reply	other threads:[~2009-08-07  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 22:19 [patch for 2.6.31? 2/2] gigaset: really fix chars_in_buffer akpm
2009-08-07  3:22 ` David Miller [this message]
2009-08-07  3:50   ` Greg KH

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=20090806.202227.224933454.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=netdev@vger.kernel.org \
    --cc=tilman@imap.cc \
    /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).