mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Andre Przywara <Andre.Przywara@arm.com>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3] x86: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Wed, 11 Mar 2015 14:36:47 +0100	[thread overview]
Message-ID: <20150311133647.GB4464@pd.tnic> (raw)
In-Reply-To: <54FF0120.1070205@arm.com>

On Tue, Mar 10, 2015 at 02:35:12PM +0000, Sudeep Holla wrote:
> My initial assumption was that it will be NULL for Intel processors
> and hence I assigned cacheinfo->priv to nb pointer unconditionally. So
> I don't have any strong opinion here.

Right, we need the NB descriptor on AMD to do L3-specific operations,
see amd_l3_disable_index() for an example.

IOW, I ended up committing this:

---
From: Sudeep Holla <sudeep.holla@arm.com>
Date: Wed, 11 Mar 2015 11:54:29 +0100
Subject: [PATCH] x86/cacheinfo: Fix cache_get_priv_group() for Intel
 processors

The private pointer provided by the cacheinfo code is used to implement
the AMD L3 cache-specific attributes using a pointer to the northbridge
descriptor. It is needed for performing L3-specific operations and for
that we need a couple of PCI devices and other service information, all
contained in the northbridge descriptor.

However, it's populated even on Intel processors for an L3 cache.
This results in failure of cacheinfo setup as shown below as
cache_get_priv_group() returns the unintialised private attributes which
are not valid for Intel processors.

------------[ cut here ]------------
WARNING: CPU: 3 PID: 1 at fs/sysfs/group.c:102
internal_create_group+0x151/0x280()
sysfs: (bin_)attrs not set by subsystem for group: index3/
Modules linked in:
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.0.0-rc3+ #1
Hardware name: Dell Inc. Precision T3600/0PTTT9, BIOS A13 05/11/2014
...
Call Trace:
  dump_stack
  warn_slowpath_common
  warn_slowpath_fmt
  internal_create_group
  sysfs_create_groups
  device_add
  cpu_device_create
  ? __kmalloc
  cache_add_dev
  cacheinfo_sysfs_init
  ? container_dev_init
  do_one_initcall
  kernel_init_freeable
  ? rest_init
  kernel_init
  ret_from_fork
  ? rest_init

This patch fixes the issue by checking if the l3 cache indices are
populated correctly (AMD-specific) before initializing the private
attributes.

Reported-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Signed-off-by: 
---
 arch/x86/kernel/cpu/intel_cacheinfo.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c b/arch/x86/kernel/cpu/intel_cacheinfo.c
index 8008bc2dd2d0..edcb0e28c336 100644
--- a/arch/x86/kernel/cpu/intel_cacheinfo.c
+++ b/arch/x86/kernel/cpu/intel_cacheinfo.c
@@ -556,7 +556,7 @@ cache_get_priv_group(struct cacheinfo *this_leaf)
 {
 	struct amd_northbridge *nb = this_leaf->priv;
 
-	if (this_leaf->level < 3)
+	if (this_leaf->level < 3 || !nb)
 		return NULL;
 
 	if (nb && nb->l3_cache.indices)
-- 
2.2.0.33.gc18b867

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2015-03-11 13:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  7:50 [PATCH RFT] " Sudeep Holla
2015-01-23 13:55 ` Thomas Gleixner
2015-01-23 18:15   ` Borislav Petkov
2015-02-23 16:36     ` Sudeep Holla
2015-02-23 18:14 ` [PATCH RFT v2] " Sudeep Holla
2015-02-24  7:58   ` Ingo Molnar
2015-02-24  9:30     ` Sudeep Holla
2015-02-24 17:57   ` Borislav Petkov
2015-02-24 18:09     ` Sudeep Holla
2015-02-24 18:58       ` Borislav Petkov
2015-03-01 22:39     ` Andre Przywara
2015-03-02 10:17       ` Sudeep Holla
2015-03-03 18:45       ` Borislav Petkov
2015-03-03 18:53         ` Tejun Heo
2015-03-03 18:57           ` Borislav Petkov
2015-03-04 11:15             ` Sudeep Holla
2015-03-04 11:27               ` Borislav Petkov
2015-03-04 11:35                 ` Sudeep Holla
2015-03-04  9:52         ` Sudeep Holla
2015-03-04 12:00   ` [PATCH v3] " Sudeep Holla
2015-03-04 12:27     ` Borislav Petkov
2015-03-05  8:16       ` Borislav Petkov
2015-03-05  9:28         ` Sudeep Holla
2015-03-10 11:37           ` Borislav Petkov
2015-03-10 11:53             ` Sudeep Holla
2015-03-10 14:22               ` Sudeep Holla
2015-03-10 14:26                 ` Borislav Petkov
2015-03-10 14:35                   ` Sudeep Holla
2015-03-11 13:36                     ` Borislav Petkov [this message]
2015-03-11 15:44                       ` Sudeep Holla
2015-03-11 20:23                         ` Borislav Petkov
2015-03-09 14:46     ` [tip:x86/cpu] x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure tip-bot for Sudeep Holla

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=20150311133647.GB4464@pd.tnic \
    --to=bp@suse.de \
    --cc=Andre.Przywara@arm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@linutronix.de \
    --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®