From: Sudeep Holla <sudeep.holla@arm.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>, Borislav Petkov <bp@suse.de>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [x86/cacheinfo] 0d55ba46bfb: WARNING: CPU: 31 PID: 1 at fs/sysfs/group.c:102 internal_create_group+0x151/0x280()
Date: Thu, 19 Mar 2015 09:32:09 +0000 [thread overview]
Message-ID: <550A9799.2080404@arm.com> (raw)
In-Reply-To: <1426732130.5570.43.camel@intel.com>
Hi Huang,
On 19/03/15 02:28, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 0d55ba46bfbee64fd2b492b87bfe2ec172e7b056 ("x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure")
>
[...]
>
> [ 8.700596] Non-volatile memory driver v1.3
> [ 8.705684] Linux agpgart interface v0.103
> [ 8.711362] ------------[ cut here ]------------
> [ 8.716832] WARNING: CPU: 31 PID: 1 at fs/sysfs/group.c:102 internal_create_group+0x151/0x280()
> [ 8.729104] sysfs: (bin_)attrs not set by subsystem for group: index3/
IIUC, a modified version(as per the discussion on that thread) of the
patch[1] posted a while ago fixed this issue. I had assumed Boris had
pulled, but seem to have missed. Boris, is that right ?
Regards,
Sudeep
[1] https://lkml.org/lkml/2015/3/10/342
next prev parent reply other threads:[~2015-03-19 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 2:28 [LKP] [x86/cacheinfo] 0d55ba46bfb: WARNING: CPU: 31 PID: 1 at fs/sysfs/group.c:102 internal_create_group+0x151/0x280() Huang Ying
2015-03-19 9:32 ` Sudeep Holla [this message]
2015-03-19 9:55 ` Borislav Petkov
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=550A9799.2080404@arm.com \
--to=sudeep.holla@arm.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@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