From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Dongyun Liu <dongyun.liu3@gmail.com>,
minchan@kernel.org, senozhatsky@chromium.org, axboe@kernel.dk,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
lincheng.yang@transsion.com, jiajun.ling@transsion.com,
ldys2014@foxmail.com, Dongyun Liu <dongyun.liu@transsion.com>
Subject: Re: [PATCH] zram: Using GFP_ATOMIC instead of GFP_KERNEL to allocate bitmap memory in backing_dev_store (fwd)
Date: Wed, 6 Dec 2023 18:53:12 +0900 [thread overview]
Message-ID: <20231206095312.GA333238@google.com> (raw)
In-Reply-To: <8bb6e568-1c79-6410-5893-781621b71331@inria.fr>
Hi,
On (23/12/06 10:33), Julia Lawall wrote:
> Hello,
>
> The warning is because kvfree is used to free memory that was allocated
> using kmalloc; kfree would be fine. But I think that the only way you can
> get to out is with bitmap being NULL, so there is no need to free it at
> all.
>
> Furthermore, it could be safer in the long term to use different labels
> for the different amounts of things that need to be freed, as done in most
> other kernel code, rather than using a single label "out".
[..]
> Date: Wed, 6 Dec 2023 16:08:49 +0800
> From: kernel test robot <lkp@intel.com>
> To: oe-kbuild@lists.linux.dev
> Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
> Subject: Re: [PATCH] zram: Using GFP_ATOMIC instead of GFP_KERNEL to allocate
> bitmap memory in backing_dev_store
>
> BCC: lkp@intel.com
> CC: oe-kbuild-all@lists.linux.dev
> In-Reply-To: <20231130152047.200169-1-dongyun.liu@transsion.com>
> References: <20231130152047.200169-1-dongyun.liu@transsion.com>
> TO: Dongyun Liu <dongyun.liu3@gmail.com>
> TO: minchan@kernel.org
> TO: senozhatsky@chromium.org
> TO: axboe@kernel.dk
> CC: linux-kernel@vger.kernel.org
> CC: linux-block@vger.kernel.org
> CC: lincheng.yang@transsion.com
> CC: jiajun.ling@transsion.com
> CC: ldys2014@foxmail.com
> CC: Dongyun Liu <dongyun.liu@transsion.com>
>
> Hi Dongyun,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on axboe-block/for-next]
> [also build test WARNING on linus/master v6.7-rc4 next-20231206]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Dongyun-Liu/zram-Using-GFP_ATOMIC-instead-of-GFP_KERNEL-to-allocate-bitmap-memory-in-backing_dev_store/20231130-233042
> base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
> patch link: https://lore.kernel.org/r/20231130152047.200169-1-dongyun.liu%40transsion.com
> patch subject: [PATCH] zram: Using GFP_ATOMIC instead of GFP_KERNEL to allocate bitmap memory in backing_dev_store
This patch won't land upstream. It was NAK-ed.
prev parent reply other threads:[~2023-12-06 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 9:33 [PATCH] zram: Using GFP_ATOMIC instead of GFP_KERNEL to allocate bitmap memory in backing_dev_store (fwd) Julia Lawall
2023-12-06 9:53 ` Sergey Senozhatsky [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=20231206095312.GA333238@google.com \
--to=senozhatsky@chromium.org \
--cc=axboe@kernel.dk \
--cc=dongyun.liu3@gmail.com \
--cc=dongyun.liu@transsion.com \
--cc=jiajun.ling@transsion.com \
--cc=julia.lawall@inria.fr \
--cc=ldys2014@foxmail.com \
--cc=lincheng.yang@transsion.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.