From: Jiri Slaby <jslaby@suse.cz>
To: Pan Xinhui <xinhuix.pan@intel.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Cc: yanmin_zhang@linux.intel.com, mnipxh@gmail.com
Subject: Re: [PATCH v2 RESEND] tty/n_gsm.c: fix a memory leak when gsmtty is removed
Date: Fri, 27 Mar 2015 09:51:08 +0100 [thread overview]
Message-ID: <551519FC.5030809@suse.cz> (raw)
In-Reply-To: <55161530.3040103@intel.com>
On 03/28/2015, 03:42 AM, Pan Xinhui wrote:
> when gsmtty_remove put dlci, it will cause memory leak if dlci->port's
> refcount is zero.
> So we do the cleanup work in .cleanup callback instead.
>
> dlci will be last put in two call chains.
> 1) gsmld_close -> gsm_cleanup_mux -> gsm_dlci_release -> dlci_put
> 2) gsmld_remove -> dlci_put
> so there is a race. the memory leak depends on the race.
>
> In call chain 2. we hit the memory leak. below comment tells.
>
> release_tty -> tty_driver_remove_tty -> gsmtty_remove -> dlci_put ->
> tty_port_destructor (WARN_ON(port->itty) and return directly)
> |
> tty->port->itty = NULL;
> |
> tty_kref_put ---> release_one_tty -> gsmtty_cleanup
> (added by our patch)
>
> So our patch fix the memory leak by doing the cleanup work after tty
> core did.
>
> Signed-off-by: Pan Xinhui <xinhuix.pan@intel.com>
Fixes: dfabf7ffa30585
Acked-by: Jiri Slaby <jslaby@suse.cz>
> ---
> Changes in v2:
> Don't use schedule_work to put dlci. Replace .remove with .cleanup
> callback.
>
> drivers/tty/n_gsm.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index c434376..bce16e4 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -3170,7 +3170,7 @@ static int gsmtty_break_ctl(struct tty_struct
> *tty, int state)
> return gsmtty_modem_update(dlci, encode);
> }
>
> -static void gsmtty_remove(struct tty_driver *driver, struct tty_struct
> *tty)
> +static void gsmtty_cleanup(struct tty_struct *tty)
> {
> struct gsm_dlci *dlci = tty->driver_data;
> struct gsm_mux *gsm = dlci->gsm;
> @@ -3178,7 +3178,6 @@ static void gsmtty_remove(struct tty_driver
> *driver, struct tty_struct *tty)
> dlci_put(dlci);
> dlci_put(gsm->dlci[0]);
> mux_put(gsm);
> - driver->ttys[tty->index] = NULL;
> }
>
> /* Virtual ttys for the demux */
> @@ -3199,7 +3198,7 @@ static const struct tty_operations gsmtty_ops = {
> .tiocmget = gsmtty_tiocmget,
> .tiocmset = gsmtty_tiocmset,
> .break_ctl = gsmtty_break_ctl,
> - .remove = gsmtty_remove,
> + .cleanup = gsmtty_cleanup,
> };
>
>
--
js
suse labs
prev parent reply other threads:[~2015-03-27 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 7:26 [PATCH] tty/n_gsm.c: fix a memory leak when gsmtty is removed Pan Xinhui
2015-03-25 7:05 ` [PATCH v2] " Pan Xinhui
2015-03-26 21:36 ` Greg KH
2015-03-28 2:42 ` [PATCH v2 RESEND] " Pan Xinhui
2015-03-27 8:51 ` Jiri Slaby [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=551519FC.5030809@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnipxh@gmail.com \
--cc=xinhuix.pan@intel.com \
--cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox