All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Anzolin <gianluca@sottospazio.it>
To: Jiri Slaby <jslaby@suse.cz>
Cc: gregkh@linuxfoundation.org, gustavo@padovan.org,
	peter@hurleysoftware.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty_port: Fix refcounting leak in tty_port_tty_hangup()
Date: Thu, 25 Jul 2013 10:14:36 +0200	[thread overview]
Message-ID: <20130725081436.GA8057@sottospazio.it> (raw)
In-Reply-To: <51F0C525.8080506@suse.cz>

On Thu, Jul 25, 2013 at 08:26:45AM +0200, Jiri Slaby wrote:
> On 07/25/2013 07:26 AM, Gianluca Anzolin wrote:
> > The function tty_port_tty_hangup() could leak a reference to the tty_struct:
> > 
> >         struct tty_struct *tty = tty_port_tty_get(port);
> > 
> >         if (tty && (!check_clocal || !C_CLOCAL(tty))) {
> >                 tty_hangup(tty);
> >                 tty_kref_put(tty);
> >         }
> > 
> > If tty != NULL and the second condition is false we never call tty_kref_put and
> > the reference is leaked.
> > 
> > Fix by always calling tty_kref_put() which accepts a NULL argument.
> > 
> > The patch fixes a regression introduced by commit aa27a094.
> > 
> > Acked-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > Signed-off-by: Gianluca Anzolin <gianluca@sottospazio.it>
> 
> Acked-by: Jiri Slaby <jslaby@suse.cz>
> 
> Thanks for the fix.
> 

Hi,

I sent this morning a newer fix changed following the instructions of Peter
Hurley. Could you apply that fix instead?

Thank you,

Gianluca

  reply	other threads:[~2013-07-25  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  5:26 [PATCH] tty_port: Fix refcounting leak in tty_port_tty_hangup() Gianluca Anzolin
2013-07-25  6:26 ` Jiri Slaby
2013-07-25  8:14   ` Gianluca Anzolin [this message]
2013-07-25  8:30     ` Gianluca Anzolin

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=20130725081436.GA8057@sottospazio.it \
    --to=gianluca@sottospazio.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@padovan.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    /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.