From: Zi Yan <ziy@nvidia.com>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Alexei Starovoitov <ast@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH V2] mm/page_alloc: skip debug_check_no_{obj,locks}_freed with FPI_TRYLOCK
Date: Mon, 09 Feb 2026 11:37:56 -0500 [thread overview]
Message-ID: <E2F7802B-F549-495F-BDBC-358A233D0939@nvidia.com> (raw)
In-Reply-To: <20260209062639.16577-1-harry.yoo@oracle.com>
On 9 Feb 2026, at 1:26, Harry Yoo wrote:
> When CONFIG_DEBUG_OBJECTS_FREE is enabled,
> debug_check_no_{obj,locks}_freed() functions are called.
>
> Since both of them spin on a lock, they are not safe to be called
> if the FPI_TRYLOCK flag is specified. This leads to a lockdep splat:
>
> ================================
> WARNING: inconsistent lock state
> 6.19.0-rc5-slab-for-next+ #326 Tainted: G N
> --------------------------------
> inconsistent {INITIAL USE} -> {IN-NMI} usage.
> kunit_try_catch/9046 [HC2[2]:SC0[0]:HE0:SE1] takes:
> ffffffff84ed6bf8 (&obj_hash[i].lock){-.-.}-{2:2}, at: __debug_check_no_obj_freed+0xe0/0x300
> {INITIAL USE} state was registered at:
> lock_acquire+0xd9/0x2f0
> _raw_spin_lock_irqsave+0x4c/0x80
> __debug_object_init+0x9d/0x1f0
> debug_object_init+0x34/0x50
> __init_work+0x28/0x40
> init_cgroup_housekeeping+0x151/0x210
> init_cgroup_root+0x3d/0x140
> cgroup_init_early+0x30/0x240
> start_kernel+0x3e/0xcd0
> x86_64_start_reservations+0x18/0x30
> x86_64_start_kernel+0xf3/0x140
> common_startup_64+0x13e/0x148
> irq event stamp: 2998
> hardirqs last enabled at (2997): [<ffffffff8298b77a>] exc_nmi+0x11a/0x240
> hardirqs last disabled at (2998): [<ffffffff8298b991>] sysvec_irq_work+0x11/0x110
> softirqs last enabled at (1416): [<ffffffff813c1f72>] __irq_exit_rcu+0x132/0x1c0
> softirqs last disabled at (1303): [<ffffffff813c1f72>] __irq_exit_rcu+0x132/0x1c0
>
> other info that might help us debug this:
> Possible unsafe locking scenario:
>
> CPU0
> ----
> lock(&obj_hash[i].lock);
> <Interrupt>
> lock(&obj_hash[i].lock);
>
> *** DEADLOCK ***
>
> Rename free_pages_prepare() to __free_pages_prepare(), add an fpi_t
> parameter, and skip those checks if FPI_TRYLOCK is set. To keep the
> fpi_t definition in mm/page_alloc.c, add a wrapper function
> free_pages_prepare() that always passes FPI_NONE and use it in
> mm/compaction.c.
>
> Fixes: 8c57b687e833 ("mm, bpf: Introduce free_pages_nolock()")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Harry Yoo <harry.yoo@oracle.com>
> ---
>
> V1 -> v2:
>
> Per Vlastimil's suggestion, rename free_pages_prepare() to
> __free_pages_prepare() instead of moving the fpi_t definition to
> mm/internal.h. __free_pages_prepare() takes fpi_t as parameter,
> free_pages_prepare() always passes FPI_NONE to __free_pages_prepare().
>
> mm/page_alloc.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
Thanks.
Acked-by: Zi Yan <ziy@nvidia.com>
Best Regards,
Yan, Zi
prev parent reply other threads:[~2026-02-09 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 6:26 Harry Yoo
2026-02-09 10:51 ` Vlastimil Babka
2026-02-09 16:37 ` Zi Yan [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=E2F7802B-F549-495F-BDBC-358A233D0939@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jackmanb@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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