From: "xinhui.pan" <xinhuix.pan@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>, Jiri Slaby <jslaby@suse.cz>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Peter Hurley <peter@hurleysoftware.com>,
mnipxh <mnipxh@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty/n_gsm.c: fix a memory leak in gsmld_open
Date: Mon, 28 Jul 2014 16:23:50 +0800 [thread overview]
Message-ID: <53D60896.5050703@intel.com> (raw)
In-Reply-To: <53D6067C.4000702@intel.com>
hi, All
thanks for reading. Below is my trigger.
----------------------------------------
#define WARN(x) do{ \
KLOG_ERROR("XINHUI",x); \
}while(0)
int main()
{
KLOG_ERROR("XINHUI", "hello world :)\n");
long fp[4];
int i = 0;
int next[4]={1,2,3,0};
do{
char path[64] = "dev/tty30";
path[strlen(path) - 1] = '0' + i;
fp[i] = open(path, O_RDWR);
if (fp[i] == -1){
WARN("mlk tty open fails\n");
return 0;
}
}while(++i < 4);
i = 0;
do{
int p = 21;
int ret = ioctl(fp[i], TIOCSETD , &p);
if (ret != 0) {
WARN("mlk tty ioctl fails\n");
}
i = next[i];
}while(1);
/* never run here, just ctrl^C */
return 0 ;
}
----------------------------------------
without this patch, running my own tests.
my result:
PROCRANK:
.....
RAM: 1993076K total, 147968K free, 708K buffers, 108340K cached, 332K shmem, 1092232K slab
AWESOME!
cat /proc/slabinfo
.....
kmalloc-2048 509700 509700 2048 16 8 : tunables 0 0 0 : slabdata 32285 32285 0
.....
AWESOME!!
thanks,
xinhui
于 2014年07月28日 16:14, xinhui.pan 写道:
> If gsmld_attach_gsm fails, the gsm is not used anymore.
> tty core will not call gsmld_close to do the cleanup work.
> tty core just restore to the tty old ldisc.
> That always causes memory leak.
>
> Signed-off-by: xinhui.pan <xinhuiX.pan@intel.com>
> Reported-by: Peter Hurley <peter@hurleysoftware.com>
> ---
> drivers/tty/n_gsm.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index 81e7ccb..6cb1a6d 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -2368,6 +2368,7 @@ static void gsmld_close(struct tty_struct *tty)
> static int gsmld_open(struct tty_struct *tty)
> {
> struct gsm_mux *gsm;
> + int ret;
>
> if (tty->ops->write == NULL)
> return -EINVAL;
> @@ -2382,7 +2383,13 @@ static int gsmld_open(struct tty_struct *tty)
>
> /* Attach the initial passive connection */
> gsm->encoding = 1;
> - return gsmld_attach_gsm(tty, gsm);
> +
> + ret = gsmld_attach_gsm(tty, gsm);
> + if (ret != 0) {
> + gsm_cleanup_mux(gsm);
> + mux_put(gsm);
> + }
> + return ret;
> }
>
> /**
>
next prev parent reply other threads:[~2014-07-28 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 8:14 [PATCH] tty/n_gsm.c: fix a memory leak in gsmld_open xinhui.pan
2014-07-28 8:23 ` xinhui.pan [this message]
2014-07-28 8:49 ` Jiri Slaby
2014-07-28 9:03 ` xinhui.pan
2014-07-28 11:32 ` xinhui.pan
2014-07-28 12:11 ` Jiri Slaby
2014-07-28 19:30 ` Peter Hurley
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=53D60896.5050703@intel.com \
--to=xinhuix.pan@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mnipxh@gmail.com \
--cc=peter@hurleysoftware.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