From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Peter Newman <peternewman@google.com>,
Babu Moger <babu.moger@amd.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: resctrl mount fail on v6.13-rc1
Date: Mon, 2 Dec 2024 14:26:48 -0800 [thread overview]
Message-ID: <868b451a-fdba-4b45-bff1-9ac1023080c8@intel.com> (raw)
In-Reply-To: <Z04pz3AlvI4o0Mr8@agluck-desk3>
Hi Tony,
On 12/2/24 1:42 PM, Luck, Tony wrote:
> Anyone better a decoding lockdep dumps then me make sense of this?
>
> All I did was build v6.13-rc1 with (among others)
>
> CONFIG_PROVE_LOCKING=y
> CONFIG_PROVE_RAW_LOCK_NESTING=y
> CONFIG_PROVE_RCU=y
>
> and then mount the resctrl filesystem:
>
> $ sudo mount -t resctrl resctrl /sys/fs/resctrl
>
> There are only trivial changes to the resctrl code between
> v6.12 (which works) and v6.13-rc1:
>
> $ git log --oneline v6.13-rc1 ^v6.12 -- arch/x86/kernel/cpu/resctrl
> 5a4b3fbb4849 Merge tag 'x86_cache_for_v6.13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> 9bce6e94c4b3 x86/resctrl: Support Sub-NUMA cluster mode SNC6
> 29eaa7958367 x86/resctrl: Slightly clean-up mbm_config_show()
>
> So something in kernfs? Or the way resctrl uses kernfs?
I am not seeing this but that may be because I am not testing with
selinux enabled. My test kernel has:
# CONFIG_SECURITY_SELINUX is not set
I am also not running with any btrfs filesystems.
Is this your usual setup in which you are seeing this the first time? Is it
perhaps possible for you to bisect?
The subject states "resctrl mount fail" - could you please confirm if
resctrl cannot be mounted in addition to the lockdep warning?
Reinette
next prev parent reply other threads:[~2024-12-02 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 21:42 Luck, Tony
2024-12-02 22:26 ` Reinette Chatre [this message]
2024-12-02 22:46 ` Luck, Tony
2024-12-03 0:03 ` Fenghua Yu
2024-12-02 22:46 ` Fenghua Yu
2024-12-03 2:47 ` Luck, Tony
2024-12-03 3:35 ` Ming Lei
2024-12-03 3:49 ` Reinette Chatre
2024-12-03 4:54 ` Reinette Chatre
2024-12-03 5:02 ` Reinette Chatre
2024-12-04 3:27 ` Ming Lei
2024-12-04 16:48 ` Reinette Chatre
2024-12-05 9:29 ` Ming Lei
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=868b451a-fdba-4b45-bff1-9ac1023080c8@intel.com \
--to=reinette.chatre@intel.com \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=tony.luck@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
all inboxes | Powered by JetHome®