linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org,  x86@kernel.org, peterz@infradead.org,
	hch@lst.de, rick.p.edgecombe@intel.com,  aaron.lu@intel.com,
	rppt@kernel.org
Subject: Re: [PATCH bpf-next v3 1/6] vmalloc: introduce execmem_alloc, execmem_free, and execmem_fill
Date: Wed, 16 Nov 2022 22:48:56 -0800	[thread overview]
Message-ID: <CAPhsuW4TcQ1bAtZcYME_c4hCr8u3E7ObpxWbdsiGCVdYnfdNgQ@mail.gmail.com> (raw)
In-Reply-To: <Y3WQEPB6FaHRXidp@bombadil.infradead.org>

On Wed, Nov 16, 2022 at 5:36 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> On Wed, Nov 16, 2022 at 05:06:16PM -0800, Song Liu wrote:
> > +static void move_vmap_to_free_text_tree(void *addr)
> > +{
> > +     struct vmap_area *va;
> > +
> > +     /* remove from vmap_area_root */
> > +     spin_lock(&vmap_area_lock);
> > +     va = __find_vmap_area((unsigned long)addr, &vmap_area_root);
> > +     if (WARN_ON_ONCE(!va)) {
> > +             spin_unlock(&vmap_area_lock);
> > +             return;
> > +     }
> > +     unlink_va(va, &vmap_area_root);
> > +     spin_unlock(&vmap_area_lock);
> > +
> > +     /* make the memory RO+X */
> > +     memset(addr, 0, va->va_end - va->va_start);
> > +     set_memory_ro(va->va_start, (va->va_end - va->va_start) >> PAGE_SHIFT);
> > +     set_memory_x(va->va_start, (va->va_end - va->va_start) >> PAGE_SHIFT);
> > +
> > +     /* add to all_text_vm */
> > +     va->vm->next = all_text_vm;
> > +     all_text_vm = va->vm;
> > +
> > +     /* add to free_text_area_root */
> > +     spin_lock(&free_text_area_lock);
> > +     merge_or_add_vmap_area_augment(va, &free_text_area_root, &free_text_area_list);
> > +     spin_unlock(&free_text_area_lock);
> > +}
>
> <-- snip -->
>
> > +void *execmem_alloc(unsigned long size, unsigned long align)
> > +{
> > +     struct vmap_area *va, *tmp;
> > +     unsigned long addr;
> > +     enum fit_type type;
> > +     int ret;
> > +
> > +     va = kmem_cache_alloc_node(vmap_area_cachep, GFP_KERNEL, NUMA_NO_NODE);
> > +     if (unlikely(!va))
> > +             return NULL;
> > +
> > +again:
> > +     preload_this_cpu_lock(&free_text_area_lock, GFP_KERNEL, NUMA_NO_NODE);
> > +     tmp = find_vmap_lowest_match(&free_text_area_root, size, align, 1, false);
> > +
> > +     if (!tmp) {
> > +             unsigned long alloc_size;
> > +             void *ptr;
> > +
> > +             spin_unlock(&free_text_area_lock);
> > +
> > +             /*
> > +              * Not enough continuous space in free_text_area_root, try
> > +              * allocate more memory. The memory is first added to
> > +              * vmap_area_root, and then moved to free_text_area_root.
> > +              */
> > +             alloc_size = roundup(size, PMD_SIZE * num_online_nodes());
> > +             ptr = __vmalloc_node_range(alloc_size, PMD_SIZE, EXEC_MEM_START,
> > +                                        EXEC_MEM_END, GFP_KERNEL, PAGE_KERNEL,
> > +                                        VM_ALLOW_HUGE_VMAP | VM_NO_GUARD,
> > +                                        NUMA_NO_NODE, __builtin_return_address(0));
> > +             if (unlikely(!ptr))
> > +                     goto err_out;
> > +
> > +             move_vmap_to_free_text_tree(ptr);
>
> It's not perfectly clear to me how we know for sure nothing can take
> this underneath our noses.

This is because ptr points to vmap_area in vmap_area_* tree. It is only
used by the user (this thread). It is like we know vmalloc memory will
not go away until we call vfree on it.

Does this make sense?

Song


  reply	other threads:[~2022-11-17  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  1:06 [PATCH bpf-next v3 0/6] execmem_alloc for BPF programs Song Liu
2022-11-17  1:06 ` [PATCH bpf-next v3 1/6] vmalloc: introduce execmem_alloc, execmem_free, and execmem_fill Song Liu
2022-11-17  1:36   ` Luis Chamberlain
2022-11-17  6:48     ` Song Liu [this message]
2022-11-17  1:06 ` [PATCH bpf-next v3 2/6] x86/alternative: support execmem_alloc() and execmem_free() Song Liu
2022-11-17  1:06 ` [PATCH bpf-next v3 3/6] selftests/vm: extend test_vmalloc to test execmem_* APIs Song Liu
2022-11-17  1:49   ` Luis Chamberlain
2022-11-17  6:41     ` Song Liu
2022-11-17 20:04       ` Luis Chamberlain
2022-11-17  1:06 ` [PATCH bpf-next v3 4/6] bpf: use execmem_alloc for bpf program and bpf dispatcher Song Liu
2022-11-17  1:52   ` Luis Chamberlain
2022-11-17  2:10     ` Alexei Starovoitov
2022-11-17 20:01       ` Luis Chamberlain
2022-11-17 20:03         ` Luis Chamberlain
2022-11-17  1:06 ` [PATCH bpf-next v3 5/6] vmalloc: introduce register_text_tail_vm() Song Liu
2022-11-17  1:06 ` [PATCH bpf-next v3 6/6] x86: use register_text_tail_vm Song Liu

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=CAPhsuW4TcQ1bAtZcYME_c4hCr8u3E7ObpxWbdsiGCVdYnfdNgQ@mail.gmail.com \
    --to=song@kernel.org \
    --cc=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=rppt@kernel.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox