[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49ff5505-5a4a-1ad5-8552-6e79a91ee8c9@suse.cz>
Date: Thu, 7 Sep 2023 08:53:14 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: "Joel Fernandes (Google)" <joel@...lfernandes.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Uladzislau Rezki <urezki@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Lorenzo Stoakes <lstoakes@...il.com>,
"Paul E. McKenney" <paulmck@...nel.org>
Cc: Zhen Lei <thunder.leizhen@...weicloud.com>, rcu@...r.kernel.org,
Zqiang <qiang.zhang1211@...il.com>, stable@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v3 1/2] mm/vmalloc: Add a safer version of find_vm_area()
for debug
Hi,
On 9/4/23 20:08, Joel Fernandes (Google) wrote:
> It is unsafe to dump vmalloc area information when trying to do so from
> some contexts. Add a safer trylock version of the same function to do a
> best-effort VMA finding and use it from vmalloc_dump_obj().
I was a bit confused by the subject which suggests a new function is added,
but it seems open-coded in its only caller. I assume it's due to evolution
of the series. Something like:
mm/vmalloc: use trylock for vmap_area_lock in vmalloc_dump_obj()
?
I also notice it's trying hard to copy everything from "vm" to temporary
variables before unlocking, presumably to prevent use-after-free, so should
that be also mentioned in the changelog?
> [applied test robot feedback on unused function fix.]
> [applied Uladzislau feedback on locking.]
>
> Reported-by: Zhen Lei <thunder.leizhen@...weicloud.com>
> Cc: Paul E. McKenney <paulmck@...nel.org>
> Cc: rcu@...r.kernel.org
> Cc: Zqiang <qiang.zhang1211@...il.com>
> Reviewed-by: Uladzislau Rezki (Sony) <urezki@...il.com>
> Fixes: 98f180837a89 ("mm: Make mem_dump_obj() handle vmalloc() memory")
> Cc: stable@...r.kernel.org
> Signed-off-by: Joel Fernandes (Google) <joel@...lfernandes.org>
> ---
> mm/vmalloc.c | 26 ++++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 93cf99aba335..2c6a0e2ff404 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4274,14 +4274,32 @@ void pcpu_free_vm_areas(struct vm_struct **vms, int nr_vms)
> #ifdef CONFIG_PRINTK
> bool vmalloc_dump_obj(void *object)
> {
> - struct vm_struct *vm;
> void *objp = (void *)PAGE_ALIGN((unsigned long)object);
> + const void *caller;
> + struct vm_struct *vm;
> + struct vmap_area *va;
> + unsigned long addr;
> + unsigned int nr_pages;
>
> - vm = find_vm_area(objp);
> - if (!vm)
> + if (!spin_trylock(&vmap_area_lock))
> + return false;
> + va = __find_vmap_area((unsigned long)objp, &vmap_area_root);
> + if (!va) {
> + spin_unlock(&vmap_area_lock);
> return false;
> + }
> +
> + vm = va->vm;
> + if (!vm) {
> + spin_unlock(&vmap_area_lock);
> + return false;
> + }
> + addr = (unsigned long)vm->addr;
> + caller = vm->caller;
> + nr_pages = vm->nr_pages;
> + spin_unlock(&vmap_area_lock);
> pr_cont(" %u-page vmalloc region starting at %#lx allocated at %pS\n",
> - vm->nr_pages, (unsigned long)vm->addr, vm->caller);
> + nr_pages, addr, caller);
> return true;
> }
> #endif
Powered by blists - more mailing lists