From: Navid Emamdoost <navid.emamdoost@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: John Hubbard <jhubbard@nvidia.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Keith Busch <keith.busch@intel.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Navid Emamdoost <emamd001@umn.edu>
Subject: Re: [PATCH] mm/gup: Fix memory leak in __gup_benchmark_ioctl
Date: Fri, 13 Dec 2019 16:39:17 -0600 [thread overview]
Message-ID: <CAEkB2EQ=sm-myT4jgJ+i0Cy5Gv=DH7vvixc1Dpz5V-Zt+P5oMQ@mail.gmail.com> (raw)
In-Reply-To: <20191213142332.d7fafc243291eac302375c32@linux-foundation.org>
On Fri, Dec 13, 2019 at 4:23 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 13 Dec 2019 13:40:15 -0800 John Hubbard <jhubbard@nvidia.com> wrote:
>
> > On 12/11/19 9:46 AM, Navid Emamdoost wrote:
> > > In the implementation of __gup_benchmark_ioctl() the allocated pages
> > > should be released before returning in case of an invalid cmd. Release
> > > pages via kvfree().
> > >
> > > Fixes: 714a3a1ebafe ("mm/gup_benchmark.c: add additional pinning methods")
> > > Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> > > ---
> > > mm/gup_benchmark.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/mm/gup_benchmark.c b/mm/gup_benchmark.c
> > > index 7dd602d7f8db..b160638f647e 100644
> > > --- a/mm/gup_benchmark.c
> > > +++ b/mm/gup_benchmark.c
> > > @@ -63,6 +63,7 @@ static int __gup_benchmark_ioctl(unsigned int cmd,
> > > NULL);
> > > break;
> > > default:
> > > + kvfree(pages);
> > > return -1;
> > > }
> > >
> >
> > Hi,
> >
> > The patch is correct, but I would like to second Ira's request for a ret value,
> > and a "goto done" to use a single place to kvfree, if you don't mind.
> >
>
> Fair enough.
>
> And let's make it return -EINVAL rather than -1, which appears to be
> -EPERM.
Sure! patch v2 has been sent.
>
> --- a/mm/gup_benchmark.c~mm-gup-fix-memory-leak-in-__gup_benchmark_ioctl-fix
> +++ a/mm/gup_benchmark.c
> @@ -26,6 +26,7 @@ static int __gup_benchmark_ioctl(unsigne
> unsigned long i, nr_pages, addr, next;
> int nr;
> struct page **pages;
> + int ret = 0;
>
> if (gup->size > ULONG_MAX)
> return -EINVAL;
> @@ -64,7 +65,8 @@ static int __gup_benchmark_ioctl(unsigne
> break;
> default:
> kvfree(pages);
> - return -1;
> + ret = -EINVAL;
> + goto out;
> }
>
> if (nr <= 0)
> @@ -86,7 +88,8 @@ static int __gup_benchmark_ioctl(unsigne
> gup->put_delta_usec = ktime_us_delta(end_time, start_time);
>
> kvfree(pages);
> - return 0;
> +out:
> + return ret;
> }
>
> static long gup_benchmark_ioctl(struct file *filep, unsigned int cmd,
> _
>
--
Navid.
next prev parent reply other threads:[~2019-12-13 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 17:46 Navid Emamdoost
2019-12-12 23:14 ` Ira Weiny
2019-12-13 21:40 ` John Hubbard
2019-12-13 22:23 ` Andrew Morton
2019-12-13 22:39 ` Navid Emamdoost [this message]
2019-12-13 22:37 ` [PATCH v2] " Navid Emamdoost
2019-12-13 23:12 ` Ira Weiny
2019-12-14 0:44 ` John Hubbard
2019-12-14 18:10 ` Markus Elfring
2019-12-16 12:18 ` David Hildenbrand
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='CAEkB2EQ=sm-myT4jgJ+i0Cy5Gv=DH7vvixc1Dpz5V-Zt+P5oMQ@mail.gmail.com' \
--to=navid.emamdoost@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=emamd001@umn.edu \
--cc=jhubbard@nvidia.com \
--cc=keith.busch@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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