From: Uladzislau Rezki <urezki@gmail.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Baoquan He <bhe@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Dave Chinner <david@fromorbit.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH 1/1] mm: vmalloc: Add a scan area of VA only once
Date: Mon, 5 Feb 2024 18:20:41 +0100 [thread overview]
Message-ID: <ZcEY6b86OijLi9Cz@pc636> (raw)
In-Reply-To: <dd3ce359-1caf-4eaf-8464-ec17284487a3@lucifer.local>
On Sun, Feb 04, 2024 at 07:44:55PM +0000, Lorenzo Stoakes wrote:
> On Fri, Feb 02, 2024 at 08:06:28PM +0100, Uladzislau Rezki (Sony) wrote:
> > Invoke a kmemleak_scan_area() function only for newly allocated
> > objects to add a scan area within that object. There is no reason
> > to add a same scan area(pointer to beginning or inside the object)
> > several times. If a VA is obtained from the cache its scan area
> > has already been associated.
> >
> > Fixes: 7db166b4aa0d ("mm: vmalloc: offload free_vmap_area_lock lock")
> > Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> > ---
> > mm/vmalloc.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > index 449f45b0e474..25a8df497255 100644
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -1882,13 +1882,13 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
> > va = kmem_cache_alloc_node(vmap_area_cachep, gfp_mask, node);
> > if (unlikely(!va))
> > return ERR_PTR(-ENOMEM);
> > - }
> >
> > - /*
> > - * Only scan the relevant parts containing pointers to other objects
> > - * to avoid false negatives.
> > - */
> > - kmemleak_scan_area(&va->rb_node, SIZE_MAX, gfp_mask);
> > + /*
> > + * Only scan the relevant parts containing pointers to other objects
> > + * to avoid false negatives.
> > + */
> > + kmemleak_scan_area(&va->rb_node, SIZE_MAX, gfp_mask);
> > + }
> >
> > retry:
> > if (addr == vend) {
> > --
> > 2.39.2
> >
>
> Looks good to me, feel free to add:
>
> Reviewed-by: Lorenzo Stoakes <lstoakes@gmail.com>
>
Appreciate for review!
--
Uladzislau Rezki
next prev parent reply other threads:[~2024-02-05 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 19:06 [PATCH 1/1] mm: vmalloc: Add a scan area of VA only once Uladzislau Rezki (Sony)
2024-02-04 19:44 ` Lorenzo Stoakes
2024-02-05 17:20 ` Uladzislau Rezki [this message]
2024-02-05 6:41 ` Christoph Hellwig
2024-02-05 17:20 ` Uladzislau Rezki
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=ZcEY6b86OijLi9Cz@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=oleksiy.avramchenko@sony.com \
--cc=willy@infradead.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.