linux-kernel - Re: x86: mce: Please revert 22223c9b417be5fd0ab2cf9ad17eb7bd1e19f7b9

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: <20091001145511.GA20933@elte.hu>
Date:	Thu, 1 Oct 2009 16:55:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Borislav Petkov <borislav.petkov@....com>,
	Borislav Petkov <petkovbb@...glemail.com>,
	Andi Kleen <andi@...stfloor.org>, x86@...nel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: x86: mce: Please revert
	22223c9b417be5fd0ab2cf9ad17eb7bd1e19f7b9

* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, 1 Oct 2009, Borislav Petkov wrote:
> > 
> > Ok, here it is, tested on two Fam10 machines here with injecting 
> > MCEs. The decoding code is now built-in by default (early_initcall 
> > requires !MODULE).
> 
> I don't think it has to require !MODULE. We could do what we do for 
> the other initcalls, ie if MODULE we turn it into just a regular 
> initcall. If that allows something like the EDAC MCE to be built as a 
> module, and people want to, then just go ahead and add the one-liner 
> to <linux/init.h>
> 
> Of course, if it _requires_ being loaded early for some other reason, 
> then that's a different issue. [...]

i think it's borderline.

The one issue that makes it nice to be core code is the fact that many 
hardware problems hit early during bootup, so having the human-readable 
decoder there has practical advantages.

I'd still like to see it nicely abstracted out, and not hardwired into 
lowlevel code. I.e. we should slowly move towards having proper chipset 
drivers in the long run. (the fact that northbridges now sit on the CPU 
die make this easier - there's fewer variations in practice.)

( One detail: if the MODULE=y case is allowed, the unregister side of 
  the callback has to be implemented. That could be .33 material i
  suspect. )

	Ingo
--
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/