From: Philipp Reisner <philipp.reisner@linbit.com>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: Lars Ellenberg <drbd-dev@lists.linbit.com>,
drbd-user@lists.linbit.com, linux-kernel@vger.kernel.org,
ldv-project@linuxtesting.org
Subject: Re: [PATCH] drbd: add module_put() on error path in drbd_proc_open()
Date: Mon, 04 Mar 2013 21:31:09 +0100 [thread overview]
Message-ID: <9738633.yZ4agRkgQF@quad> (raw)
In-Reply-To: <1362173982-26454-1-git-send-email-khoroshilov@ispras.ru>
Hi Alexey,
Thanks a lot! I have put it into our tree.
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git
I intend to get it into the 3.10 merge window.
Best,
Phil
> If single_open() fails in drbd_proc_open(), module refcount is left
> incremented. The patch adds module_put() on the error path.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> ---
> drivers/block/drbd/drbd_proc.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/block/drbd/drbd_proc.c b/drivers/block/drbd/drbd_proc.c
> index 56672a6..30fe0a5 100644
> --- a/drivers/block/drbd/drbd_proc.c
> +++ b/drivers/block/drbd/drbd_proc.c
> @@ -313,8 +313,14 @@ static int drbd_seq_show(struct seq_file *seq, void *v)
>
> static int drbd_proc_open(struct inode *inode, struct file *file)
> {
> - if (try_module_get(THIS_MODULE))
> - return single_open(file, drbd_seq_show, PDE(inode)->data);
> + int err;
> +
> + if (try_module_get(THIS_MODULE)) {
> + err = single_open(file, drbd_seq_show, PDE(inode)->data);
> + if (err)
> + module_put(THIS_MODULE);
> + return err;
> + }
> return -ENODEV;
> }
prev parent reply other threads:[~2013-03-04 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 21:39 [PATCH] drbd: add module_put() on error path in drbd_proc_open() Alexey Khoroshilov
2013-03-04 20:31 ` Philipp Reisner [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=9738633.yZ4agRkgQF@quad \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=drbd-user@lists.linbit.com \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox