From: Oliver Neukum <oneukum@suse.com> To: gregKH@linuxfoundation.org, miquel@df.uba.ar, linux-usb@vger.kernel.org Cc: Oliver Neukum <oneukum@suse.com> Subject: [2/3] rio500: fix memeory leak in close after disconnect Date: Tue, 30 Apr 2019 16:23:25 +0200 [thread overview] Message-ID: <20190430142326.25815-2-oneukum@suse.com> (raw) If a disconnected device is closed, rio_close() must free the buffers. Signed-off-by: Oliver Neukum <oneukum@suse.com> --- drivers/usb/misc/rio500.c | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/drivers/usb/misc/rio500.c b/drivers/usb/misc/rio500.c index a4b6fbea975f..20c3eb0af7ad 100644 --- a/drivers/usb/misc/rio500.c +++ b/drivers/usb/misc/rio500.c @@ -86,9 +86,22 @@ static int close_rio(struct inode *inode, struct file *file) { struct rio_usb_data *rio = &rio_instance; - rio->isopen = 0; + /* against disconnect() */ + mutex_lock(&rio500_mutex); + mutex_lock(&(rio->lock)); - dev_info(&rio->rio_dev->dev, "Rio closed.\n"); + rio->isopen = 0; + if (!rio->present) { + /* cleanup has been delayed */ + kfree(rio->ibuf); + kfree(rio->obuf); + rio->ibuf = NULL; + rio->obuf = NULL; + } else { + dev_info(&rio->rio_dev->dev, "Rio closed.\n"); + } + mutex_unlock(&(rio->lock)); + mutex_unlock(&rio500_mutex); return 0; }
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Neukum <oneukum@suse.com> To: gregKH@linuxfoundation.org, miquel@df.uba.ar, linux-usb@vger.kernel.org Cc: Oliver Neukum <oneukum@suse.com> Subject: [PATCH 2/3] rio500: fix memeory leak in close after disconnect Date: Tue, 30 Apr 2019 16:23:25 +0200 [thread overview] Message-ID: <20190430142326.25815-2-oneukum@suse.com> (raw) Message-ID: <20190430142325.4J5QNzoW_7lpe30dk6jewDMVvk4bmxoH_hF49V4wrIc@z> (raw) In-Reply-To: <20190430142326.25815-1-oneukum@suse.com> If a disconnected device is closed, rio_close() must free the buffers. Signed-off-by: Oliver Neukum <oneukum@suse.com> --- drivers/usb/misc/rio500.c | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/drivers/usb/misc/rio500.c b/drivers/usb/misc/rio500.c index a4b6fbea975f..20c3eb0af7ad 100644 --- a/drivers/usb/misc/rio500.c +++ b/drivers/usb/misc/rio500.c @@ -86,9 +86,22 @@ static int close_rio(struct inode *inode, struct file *file) { struct rio_usb_data *rio = &rio_instance; - rio->isopen = 0; + /* against disconnect() */ + mutex_lock(&rio500_mutex); + mutex_lock(&(rio->lock)); - dev_info(&rio->rio_dev->dev, "Rio closed.\n"); + rio->isopen = 0; + if (!rio->present) { + /* cleanup has been delayed */ + kfree(rio->ibuf); + kfree(rio->obuf); + rio->ibuf = NULL; + rio->obuf = NULL; + } else { + dev_info(&rio->rio_dev->dev, "Rio closed.\n"); + } + mutex_unlock(&(rio->lock)); + mutex_unlock(&rio500_mutex); return 0; } -- 2.16.4
next reply other threads:[~2019-04-30 14:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-30 14:23 Oliver Neukum [this message] 2019-04-30 14:23 ` [PATCH 2/3] rio500: fix memeory leak in close after disconnect Oliver Neukum -- strict thread matches above, loose matches on Subject: below -- 2019-04-30 14:47 [1/3] rio500: refuse more than one device at a time Alan Stern 2019-04-30 14:47 ` [PATCH 1/3] " Alan Stern 2019-04-30 14:23 [3/3] rio500: simplify locking Oliver Neukum 2019-04-30 14:23 ` [PATCH 3/3] " Oliver Neukum 2019-04-30 14:23 [1/3] rio500: refuse more than one device at a time Oliver Neukum 2019-04-30 14:23 ` [PATCH 1/3] " Oliver Neukum
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=20190430142326.25815-2-oneukum@suse.com \ --to=oneukum@suse.com \ --cc=gregKH@linuxfoundation.org \ --cc=linux-usb@vger.kernel.org \ --cc=miquel@df.uba.ar \ /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: linkBe 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.