From: Catalin Marinas <catalin.marinas@arm.com>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Waiman Long <longman@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kmemleak: Avoid RCU stalls when freeing metadata for per-CPU pointers
Date: Wed, 6 Dec 2023 11:22:22 +0000 [thread overview]
Message-ID: <ZXBZbopxmmJFxO6x@arm.com> (raw)
In-Reply-To: <20231202075055.1142-1-hdanton@sina.com>
On Sat, Dec 02, 2023 at 03:50:55PM +0800, Hillf Danton wrote:
> On Fri, 1 Dec 2023 19:08:29 +0000 Catalin Marinas <catalin.marinas@arm.com>
> > @@ -1472,14 +1474,27 @@ static void scan_object(struct kmemleak_object *object)
> > /* already freed object */
> > goto out;
> >
> > - obj_ptr = object->flags & OBJECT_PHYS ?
> > - __va((phys_addr_t)object->pointer) :
> > - (void *)object->pointer;
> > + if (object->flags & OBJECT_PERCPU) {
> > + unsigned int cpu;
> >
> > - if (hlist_empty(&object->area_list) ||
> > + for_each_possible_cpu(cpu) {
> > + void *start = per_cpu_ptr((void __percpu *)object->pointer, cpu);
> > + void *end = start + object->size;
> > +
> > + scan_block(start, end, object);
> > +
> > + raw_spin_unlock_irqrestore(&object->lock, flags);
> > + cond_resched();
> > + raw_spin_lock_irqsave(&object->lock, flags);
>
> Nit, spin_lock/unlock can be collapsed into need_resched().
>
> if (need_resched()) {
> raw_spin_unlock_irqrestore(&object->lock, flags);
> cond_resched();
> raw_spin_lock_irqsave(&object->lock, flags);
> }
The reason I'd not do this is that we also want the interrupts to be
re-enabled regularly. Keeping them disabled may not even mark the
current thread as need_resched().
--
Catalin
prev parent reply other threads:[~2023-12-06 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 19:08 Catalin Marinas
2023-12-01 22:22 ` Waiman Long
2023-12-06 11:31 ` Catalin Marinas
2023-12-02 7:50 ` Hillf Danton
2023-12-06 11:22 ` Catalin Marinas [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=ZXBZbopxmmJFxO6x@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
/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