All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 1/2] hwmon: (nct6775) Add missing sysfs attibute initialization
Date: Sun, 31 May 2015 22:40:18 +0000	[thread overview]
Message-ID: <556B8DD2.3010706@roeck-us.net> (raw)
In-Reply-To: <1432829756-14595-1-git-send-email-linux@roeck-us.net>

On 05/31/2015 03:25 PM, Alexey Orishko wrote:
> On Fri, May 29, 2015 at 10:49 AM, Jean Delvare <jdelvare@suse.de> wrote:
>> On Thu, 28 May 2015 09:15:55 -0700, Guenter Roeck wrote:
>>> The following error message is seen when loading the nct6775 driver
>>> with DEBUG_LOCK_ALLOC enabled.
>>>
>>> BUG: key ffff88040b2f0030 not in .data!
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 0 PID: 186 at kernel/locking/lockdep.c:2988
>>>                                lockdep_init_map+0x469/0x630()
>>> DEBUG_LOCKS_WARN_ON(1)
>>>
>>> Caused by a missing call to sysfs_attr_init() when initializing
>>> sysfs attributes.
>>>
>>> Reported-by: Alexey Orishko <alexey.orishko@gmail.com>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

[ ... ]

>>
>> Reviewed-by: Jean Delvare <jdelvare@suse.de>
>
> Tested on ASRock E3C222D4U motherboard with kernel 4.0.3; reported
> problem is fixed.
> Tested-by: Alexey Orishko <alexey.orishko@gmail.com>
>
Hi Alexey,

Great, thanks a lot for testing!

The fix is already available in mainline, and should eventually find its way into 4.0.x.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2015-05-31 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 16:15 [lm-sensors] [PATCH 1/2] hwmon: (nct6775) Add missing sysfs attibute initialization Guenter Roeck
2015-05-29  8:49 ` Jean Delvare
2015-05-31 22:25 ` Alexey Orishko
2015-05-31 22:40 ` Guenter Roeck [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=556B8DD2.3010706@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.