linux-kernel - Re: [PATCH 07/14] mce3: pass mce info to EDAC for decoding

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: <526340.68353.qm@web50103.mail.re2.yahoo.com>
Date:	Mon, 20 Jul 2009 14:02:10 -0700 (PDT)
From:	Doug Thompson <norsk5@...oo.com>
To:	Andi Kleen <andi@...stfloor.org>, "H. Peter Anvin" <hpa@...or.com>
Cc:	Borislav Petkov <borislav.petkov@....com>, mingo@...e.hu,
	tglx@...utronix.de, aris@...hat.com, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCH 07/14] mce3: pass mce info to EDAC for decoding



--- On Mon, 7/20/09, H. Peter Anvin <hpa@...or.com> wrote:

> From: H. Peter Anvin <hpa@...or.com>
> Subject: Re: [PATCH 07/14] mce3: pass mce info to EDAC for decoding
> To: "Andi Kleen" <andi@...stfloor.org>
> Cc: "Doug Thompson" <norsk5@...oo.com>, "Borislav Petkov" <borislav.petkov@....com>, mingo@...e.hu, tglx@...utronix.de, aris@...hat.com, linux-kernel@...r.kernel.org, x86@...nel.org
> Date: Monday, July 20, 2009, 2:17 PM
> Andi Kleen wrote:
> >> The goal is to have a default handler within the
> kernel and a more specific handler in a module after it has
> loaded. Using the weak symbol as a mechanism to do that. I
> haven't used that, so I don't know if it works.
> > 
> > weak symbols don't work over kernel modules.
> > 
> 
> For modules, you typically have to have a callback to
> update an internal
> function pointer.  If you think about it, it's pretty
> obvious -- a weak
> symbol changes the behavior at link time, but it's still a
> static call.
>  If you want modules to change the behavior, you're talking
> about a
> *dynamic* change -- the call will point to different things
> at different
> points in time -- so you need another mechanism, i.e.
> function pointers.
> 
>     -hpa

Thanks, that is exactly what I just posted in another reply.

now I understand weak symbols a bit better now as well

doug t 
--
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/