From: David Hildenbrand <david@redhat.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Yang Li <yang.lee@linux.alibaba.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [ammarfaizi2-block:akpm/mm/mm-stable 29/237] mm/gup_test.c:257:13-14: WARNING kvmalloc is used to allocate this memory at line 248 (fwd)
Date: Mon, 12 Dec 2022 17:40:21 +0100 [thread overview]
Message-ID: <590404d8-4cb4-839e-c8a0-558fa4d059c4@redhat.com> (raw)
In-Reply-To: <bea909-677b-c1f1-6f31-2dd237e7516@inria.fr>
On 12.12.22 17:26, Julia Lawall wrote:
> The concern is that pages is allocated with kvcalloc, but freed later
> using kfree.
>
Indeed, that's wrong. Will send a fix. Thanks!
> julia
>
> ---------- Forwarded message ----------
> Date: Sat, 10 Dec 2022 22:02:56 +0800
> From: kernel test robot <lkp@intel.com>
> To: oe-kbuild@lists.linux.dev
> Cc: lkp@intel.com, Julia Lawall <julia.lawall@lip6.fr>
> Subject: [ammarfaizi2-block:akpm/mm/mm-stable 29/237] mm/gup_test.c:257:13-14:
> WARNING kvmalloc is used to allocate this memory at line 248
>
> BCC: lkp@intel.com
> CC: oe-kbuild-all@lists.linux.dev
> CC: Ammar Faizi <ammarfaizi2@gnuweeb.org>
> CC: "GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
> TO: David Hildenbrand <david@redhat.com>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: Linux Memory Management List <linux-mm@kvack.org>
> CC: Yang Li <yang.lee@linux.alibaba.com>
>
> tree: https://github.com/ammarfaizi2/linux-block akpm/mm/mm-stable
> head: 3b91010500eba3601e906b0e92cf84fab4d895d1
> commit: c77369b437f983a862bb6741814670d4ad38478c [29/237] mm/gup_test: start/stop/read functionality for PIN LONGTERM test
> :::::: branch date: 11 hours ago
> :::::: commit date: 5 weeks ago
> config: arm-randconfig-c44-20221209
> compiler: arm-linux-gnueabi-gcc (GCC) 12.1.0
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Reported-by: Julia Lawall <julia.lawall@lip6.fr>
>
> cocci warnings: (new ones prefixed by >>)
>>> mm/gup_test.c:257:13-14: WARNING kvmalloc is used to allocate this memory at line 248
>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2022-12-12 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:26 Julia Lawall
2022-12-12 16:40 ` David Hildenbrand [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=590404d8-4cb4-839e-c8a0-558fa4d059c4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=julia.lawall@inria.fr \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yang.lee@linux.alibaba.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