From: Jiri Olsa <olsajiri@gmail.com>
To: Pei Xiao <xiaopei01@kylinos.cn>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] bpf: Use refcount_t instead of atomic_t for mmap_count
Date: Mon, 30 Dec 2024 17:40:48 +0100 [thread overview]
Message-ID: <Z3LNEHfLmtSi4wpO@krava> (raw)
In-Reply-To: <6ecce439a6bc81adb85d5080908ea8959b792a50.1735542814.git.xiaopei01@kylinos.cn>
On Mon, Dec 30, 2024 at 03:16:55PM +0800, Pei Xiao wrote:
> Use an API that resembles more the actual use of mmap_count.
I'm not sure I understand the issue, could you provide more details?
thanks,
jirka
>
> Found by cocci:
> kernel/bpf/arena.c:245:6-25: WARNING: atomic_dec_and_test variation before object free at line 249.
>
> Fixes: b90d77e5fd78 ("bpf: Fix remap of arena.")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202412292037.LXlYSHKl-lkp@intel.com/
> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
> ---
> kernel/bpf/arena.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/bpf/arena.c b/kernel/bpf/arena.c
> index 945a5680f6a5..8caf56a308d9 100644
> --- a/kernel/bpf/arena.c
> +++ b/kernel/bpf/arena.c
> @@ -218,7 +218,7 @@ static u64 arena_map_mem_usage(const struct bpf_map *map)
> struct vma_list {
> struct vm_area_struct *vma;
> struct list_head head;
> - atomic_t mmap_count;
> + refcount_t mmap_count;
> };
>
> static int remember_vma(struct bpf_arena *arena, struct vm_area_struct *vma)
> @@ -228,7 +228,7 @@ static int remember_vma(struct bpf_arena *arena, struct vm_area_struct *vma)
> vml = kmalloc(sizeof(*vml), GFP_KERNEL);
> if (!vml)
> return -ENOMEM;
> - atomic_set(&vml->mmap_count, 1);
> + refcount_set(&vml->mmap_count, 1);
> vma->vm_private_data = vml;
> vml->vma = vma;
> list_add(&vml->head, &arena->vma_list);
> @@ -239,7 +239,7 @@ static void arena_vm_open(struct vm_area_struct *vma)
> {
> struct vma_list *vml = vma->vm_private_data;
>
> - atomic_inc(&vml->mmap_count);
> + refcount_inc(&vml->mmap_count);
> }
>
> static void arena_vm_close(struct vm_area_struct *vma)
> @@ -248,7 +248,7 @@ static void arena_vm_close(struct vm_area_struct *vma)
> struct bpf_arena *arena = container_of(map, struct bpf_arena, map);
> struct vma_list *vml = vma->vm_private_data;
>
> - if (!atomic_dec_and_test(&vml->mmap_count))
> + if (!refcount_dec_and_test(&vml->mmap_count))
> return;
> guard(mutex)(&arena->lock);
> /* update link list under lock */
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2024-12-30 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 7:16 [PATCH] bpf: Use refcount_t instead of atomic_t for mmap_count Pei Xiao
2024-12-30 16:40 ` Jiri Olsa [this message]
2024-12-31 3:00 ` Pei Xiao
2024-12-31 4:20 ` patchwork-bot+netdevbpf
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=Z3LNEHfLmtSi4wpO@krava \
--to=olsajiri@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=xiaopei01@kylinos.cn \
/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