linux-kernel - Re: threshold_init_device/kobject_uevent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440801252204g61e05a23s10ca56c000a6635d@mail.gmail.com>
Date:	Fri, 25 Jan 2008 22:04:19 -0800
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Greg KH" <gregkh@...e.de>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: threshold_init_device/kobject_uevent_env oops

On Jan 25, 2008 2:50 PM, Greg KH <gregkh@...e.de> wrote:
> On Fri, Jan 25, 2008 at 02:47:11PM -0800, Greg KH wrote:
> > On Fri, Jan 25, 2008 at 11:35:56PM +0100, Ingo Molnar wrote:
> > >
> > > * Greg KH <gregkh@...e.de> wrote:
> > >
> > > > On Fri, Jan 25, 2008 at 01:05:40PM -0800, Yinghai Lu wrote:
> > > > > current linus tree + x86.git
> > > > >
> > > > > got
> > > > >
> > > > > Calling initcall 0xffffffff80b93d98: threshold_init_device+0x0/0x3f()
> > > > > BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
> > > > > IP: [<ffffffff80458e20>] kobject_uevent_env+0x2a/0x3d9
> > > >
> > > > Does this happen on just Linus's tree?
> > > >
> > > > Can you send me a .config file for this?
> > > >
> > > > What is threshold_init()?  Is it something new in the x86.git tree?
> > >
> > > no. A quick grep shows that it is in a file that _your_ changes in
> > > Linus' latest have touched:
> > >
> > >   arch/x86/kernel/cpu/mcheck/mce_amd_64.c
> >
> > Ok, those are pretty much just search/and/replace type changes, but I
> > have been running x86-64 boxes with these changes in place.
>
> Oh wait, I do see a change.  We are now (finally) emitting a kobject
> uevent for these devices, which somehow the code can't handle properly.
>
> Let me go poke this some more, unfortunatly I don't have any AMD 64
> boxes here anymore, only Intel based processors, so I can't run this
> module...

it only happens with AMD Quad Core CPU or Fam 10h.

works well with AMD opteron Rev E, and Rev F.

So you may need have access to new system with quad core cpu.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/