public inbox for [email protected]
 help / color / mirror / Atom feed
From: David Gow <[email protected]>
To: Dan Carpenter <[email protected]>
Cc: [email protected], Daniel Latypov <[email protected]>,
	 kernel test robot <[email protected]>,
	[email protected],
	 "GNU/Weeb Mailing List" <[email protected]>,
	 Linux Kernel Mailing List <[email protected]>,
	Shuah Khan <[email protected]>,
	 Brendan Higgins <[email protected]>
Subject: Re: [ammarfaizi2-block:shuah/linux-kselftest/kunit 4/16] lib/kunit/executor.c:78 kunit_filter_tests() warn: possible memory leak of 'copy'
Date: Tue, 12 Jul 2022 21:29:55 +0800	[thread overview]
Message-ID: <CABVgOSmvU1tOHBQDOr9vT-SSaM1k--mjck1-T-M_vWnDtWecDA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Tue, Jul 12, 2022 at 8:51 PM Dan Carpenter <[email protected]> wrote:
>
> tree:   https://github.com/ammarfaizi2/linux-block shuah/linux-kselftest/kunit
> head:   7635778bac7e46458392c1261e3916e8e9e86860
> commit: d2fbdde838f270377de4fc20e919aac3941ea55f [4/16] kunit: use kmemdup in kunit_filter_tests(), take suite as const
> config: arc-randconfig-m031-20220707 (https://download.01.org/0day-ci/archive/20220710/[email protected]/config)
> compiler: arc-elf-gcc (GCC) 11.3.0
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <[email protected]>
> Reported-by: Dan Carpenter <[email protected]>
>
> smatch warnings:
> lib/kunit/executor.c:78 kunit_filter_tests() warn: possible memory leak of 'copy'
>
> vim +/copy +78 lib/kunit/executor.c

Thanks: clang-analyzer also picked this up here:
https://lore.kernel.org/all/[email protected]/

(... snip ...)

> a127b154a8f2317 Daniel Latypov 2021-09-14  76   filtered = kcalloc(n + 1, sizeof(*filtered), GFP_KERNEL);
> a02353f491622e4 Daniel Latypov 2022-05-11  77   if (!filtered)
> a02353f491622e4 Daniel Latypov 2022-05-11 @78           return ERR_PTR(-ENOMEM);
>
> kfree(copy)?  Is the burden of random devs looking at this warning
> forever more than the burden of adding a kfree()?  Hard to measure.
>

I mean, it's the burden of not only adding a kfree(), but also a
couple of {}s. :-)

Regardless, this patch should add them:
https://lore.kernel.org/linux-kselftest/[email protected]/

> a127b154a8f2317 Daniel Latypov 2021-09-14  79
> a127b154a8f2317 Daniel Latypov 2021-09-14  80   n = 0;
> a127b154a8f2317 Daniel Latypov 2021-09-14  81   kunit_suite_for_each_test_case(suite, test_case) {
> a127b154a8f2317 Daniel Latypov 2021-09-14  82           if (!test_glob || glob_match(test_glob, test_case->name))
> a127b154a8f2317 Daniel Latypov 2021-09-14  83                   filtered[n++] = *test_case;
> a127b154a8f2317 Daniel Latypov 2021-09-14  84   }
> a127b154a8f2317 Daniel Latypov 2021-09-14  85
> a127b154a8f2317 Daniel Latypov 2021-09-14  86   copy->test_cases = filtered;
> a127b154a8f2317 Daniel Latypov 2021-09-14  87   return copy;
> a127b154a8f2317 Daniel Latypov 2021-09-14  88  }
>

Cheers,
-- David

      reply	other threads:[~2022-07-12 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 12:50 [ammarfaizi2-block:shuah/linux-kselftest/kunit 4/16] lib/kunit/executor.c:78 kunit_filter_tests() warn: possible memory leak of 'copy' Dan Carpenter
2022-07-12 13:29 ` David Gow [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=CABVgOSmvU1tOHBQDOr9vT-SSaM1k--mjck1-T-M_vWnDtWecDA@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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