On Tue, Dec 16, 2014 at 5:08 AM, Corey Minyard <cminy...@mvista.com> wrote:
> On 12/15/2014 08:53 PM, Alexei Starovoitov wrote:
>> On Fri, Dec 12, 2014 at 8:04 PM, Corey Minyard <cminy...@mvista.com> wrote:
>>> On 12/11/2014 09:20 PM, 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 2ed09fc090fc0488e2ab27604a141679fe2ef610 ("ipmi: clean up the
>>>> device handling for the bmc device")
>>> Thanks. The surprising thing is that this didn't give an error before.
>>>
>>> But this should be fixed in linux-next the next time.
>> when specifically? Is there a fix already?
>> Quite annoying to see this every boot:
>> [ 4.778018] BUG: key ffff88046458fe20 not in .data!
>> [ 4.778021] ------------[ cut here ]------------
>> [ 4.778061] WARNING: CPU: 1 PID: 1428 at
>> ../kernel/locking/lockdep.c:2991 lockdep_init_map+0x4cd/0x500()
> Yes, should be fixed by:
>
> commit 693726299ba87a6e267993806bc1320a266e5c5e
> Author: Corey Minyard <cminy...@mvista.com>
> Date: Fri Dec 12 19:06:07 2014 -0600
>
> ipmi: Finish cleanup of BMC attributes
>
> which should be in linux-next now. I was able to reproduce and verify
> that this fixed it. I've verified that the branch is correct in the
> repository.
thanks. cleared the warning for me as well:
Tested-by: Alexei Starovoitov <a...@plumgrid.com>
Are you planning to send a pull request
before the merge window is over or for rc2 ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
