From: Douglas Gilbert <dgilbert@interlog.com>
To: Li Bin <huawei.libin@huawei.com>,
jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
xiexiuqi@huawei.com
Subject: Re: [PATCH] scsi: sg: fix memory leak in sg_build_indirect
Date: Mon, 13 Apr 2020 18:15:29 -0400 [thread overview]
Message-ID: <8a11ba5c-3836-0d95-7f70-7dc32bda95c1@interlog.com> (raw)
In-Reply-To: <1586777552-17524-1-git-send-email-huawei.libin@huawei.com>
On 2020-04-13 7:32 a.m., Li Bin wrote:
> Fix a memory leak when there have failed, that we should free the pages
> under the condition rem_sz > 0.
May I paraphrase the above:
"Fix a memory leak that occurs when alloc_pages() succeeds several
times before failing. This condition is noticed when rem_sz > 0."
>
> Signed-off-by: Li Bin <huawei.libin@huawei.com>
> ---
> drivers/scsi/sg.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/sg.c b/drivers/scsi/sg.c
> index 4e6af592..8441ac5 100644
> --- a/drivers/scsi/sg.c
> +++ b/drivers/scsi/sg.c
> @@ -1959,8 +1959,12 @@ static long sg_compat_ioctl(struct file *filp, unsigned int cmd_in, unsigned lon
It is the sg_build_indirect() function not sg_compat_ioctl() as suggested
above by git. Can be get a replacement for git :-)
> k, rem_sz));
>
> schp->bufflen = blk_size;
> - if (rem_sz > 0) /* must have failed */
> + if (rem_sz > 0) { /* must have failed */
> + for (i = 0; i < k; i++)
> + __free_pages(schp->pages[i], order);
> +
> return -ENOMEM;
It is easier, and less code, to replace 'return -ENOMEM'; with
'goto out'. Or even simpler:
if (likely(rem_sz == 0))
return 0;
out:
........
Doug Gilbert
BTW I spotted this one during the sg driver rewrite and fixed it.
Note that this bug and several others like it won't be fixed by
me while the sg driver rewrite is pending.
> + }
> return 0;
> out:
> for (i = 0; i < k; i++)
>
next prev parent reply other threads:[~2020-04-13 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 11:32 Li Bin
2020-04-13 22:15 ` Douglas Gilbert [this message]
2020-04-13 19:35 Markus Elfring
2020-04-14 1:39 ` Douglas Gilbert
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=8a11ba5c-3836-0d95-7f70-7dc32bda95c1@interlog.com \
--to=dgilbert@interlog.com \
--cc=huawei.libin@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=xiexiuqi@huawei.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
Powered by JetHome