From: Jarkko Sakkinen <jarkko@kernel.org>
To: Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: reinette.chatre@intel.com, tony.luck@intel.com,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org
Subject: Re: [PATCH v7 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node
Date: Mon, 18 Oct 2021 16:35:12 +0300 [thread overview]
Message-ID: <eee87b139519684c1b2eb7d5f259580b29fc6841.camel@kernel.org> (raw)
In-Reply-To: <20211008203308.20963-2-jarkko@kernel.org>
On Fri, 2021-10-08 at 23:33 +0300, Jarkko Sakkinen wrote:
> +static void sgx_numa_exit(void)
> +{
> + struct device *dev;
> + int nid;
> +
> + for (nid = 0; nid < num_possible_nodes(); nid++) {
> + dev = &node_devices[nid]->dev;
> + if (dev)
> + sysfs_remove_group(&dev->kobj, &sgx_node_attr_group);
> + }
> +}
> +
> +static bool sgx_numa_init(void)
> +{
> + struct sgx_numa_node *node;
> + int nid;
> + int ret;
> +
> + for (nid = 0; nid < num_possible_nodes(); nid++) {
> + if (!sgx_numa_nodes[nid].size)
> + continue;
> +
> + node = &sgx_numa_nodes[nid];
> + node->dev = &node_devices[nid]->dev;
> +
> + ret = sysfs_create_group(&node->dev->kobj, &sgx_node_attr_group);
> + if (ret) {
> + sgx_numa_exit();
> + return false;
> + }
> + }
Here's a mistake: node->dev should be only set after sysfe_create_group().
Otherwise, sysfs_remove_group() will issue a warning in sgx_numa_exit(), when
sgx_create_group() is unsuccessful, because the group does not exist.
I'll fix this, and send a new version.
/Jarkko
prev parent reply other threads:[~2021-10-18 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 20:33 [PATCH v7 1/2] x86/sgx: Rename fallback labels in sgx_init() Jarkko Sakkinen
2021-10-08 20:33 ` [PATCH v7 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node Jarkko Sakkinen
2021-10-18 13:35 ` Jarkko Sakkinen [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=eee87b139519684c1b2eb7d5f259580b29fc6841.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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 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®