From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] ref_tracker: do xarray and workqueue job initializations earlier
Date: Fri, 27 Jun 2025 14:43:53 -0700 [thread overview]
Message-ID: <20250627144353.57ee3f18@kernel.org> (raw)
In-Reply-To: <20250626-reftrack-dbgfs-v1-1-812102e2a394@kernel.org>
On Thu, 26 Jun 2025 08:52:14 -0400 Jeff Layton wrote:
> The kernel test robot reported an oops that occurred when attempting to
> deregister a dentry from the xarray during subsys_initcall().
>
> The ref_tracker xarrays and workqueue job are being initialized in
> late_initcall() which is too late. Move those to postcore_initcall()
> instead.
Applied to net-next (on top of an -rc tag again, if anyone else
needs it). Thanks!
prev parent reply other threads:[~2025-06-27 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 12:52 [PATCH] ref_tracker: do xarray and workqueue job initializations earlier Jeff Layton
2025-06-27 21:43 ` Jakub Kicinski [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=20250627144353.57ee3f18@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.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;
as well as URLs for NNTP newsgroup(s).