All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Joseph Barrow <D.Barow-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
To: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: Linux USB kernel mailing list
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux netdev Mailing list
	<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux Serial
	<linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 01/02] hso patch to fix a -EIO from opening a hso serial device
Date: Wed, 14 Jan 2009 13:40:34 +0100	[thread overview]
Message-ID: <496DDD42.6060601@option.com> (raw)
In-Reply-To: <20090114113828.7b9f59ca-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>

Hi Alan,
Your fix works too I suspect better than mine & since you've a better idea of what
you are doing with tty layer than I do we'll stick with
your fix.

Do you want me to switch off the low latency stuff in the
driver?

I also need to investigate the tty_kref_put & tty_kref_get
& when it was added to the kernel so I can fix stuff for our
internal driver



Alan Cox wrote:
> On Wed, 14 Jan 2009 12:22:31 +0100
> Denis Joseph Barrow <D.Barow-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org> wrote:
> 
>> Hi All,
>> This is an important patch the linux-2.6.29-rc1 driver with itworks much
>> better than it did.
> 
> How about this. 
> 
> tty: Fix a kref leak in the HSO driver on re-open
> 
> From: Alan Cox <alan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> 
> ---
> 
>  drivers/net/usb/hso.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> 
> diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
> index c4918b8..9df04dd 100644
> --- a/drivers/net/usb/hso.c
> +++ b/drivers/net/usb/hso.c
> @@ -1297,6 +1297,7 @@ static int hso_serial_open(struct tty_struct *tty, struct file *filp)
>  	/* setup */
>  	spin_lock_irq(&serial->serial_lock);
>  	tty->driver_data = serial;
> +	tty_kref_put(serial->tty);
>  	serial->tty = tty_kref_get(tty);
>  	spin_unlock_irq(&serial->serial_lock);
>  


-- 
best regards,
D.J. Barrow

Linux Kernel Developer
Option NV, Gaston Geenslaan 14, 3001 Leuven, Belgium
 
T: +32 16 311 621
F: +32 16 207 164
d.barow-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org
www.option.com

Disclaimer:
http://www.option.com/company/disclaimer.shtml
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-01-14 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:22 [PATCH 01/02] hso patch to fix a -EIO from opening a hso serial device Denis Joseph Barrow
     [not found] ` <496DCAF7.9080906-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
2009-01-14 11:38   ` Alan Cox
     [not found]     ` <20090114113828.7b9f59ca-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2009-01-14 12:40       ` Denis Joseph Barrow [this message]
2009-01-14 13:04         ` Alan Cox
2009-01-15  5:14     ` David Miller

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=496DDD42.6060601@option.com \
    --to=d.barow-x9gzzrpc1qbqt0dzr+alfa@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.