linux-kernel - RE: [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (v2)

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]

Date:	Thu, 24 May 2012 16:15:02 +0000
From:	"Liu, Jinsong" <jinsong.liu@...el.com>
To:	Borislav Petkov <bp@...64.org>
CC:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	"Luck, Tony" <tony.luck@...el.com>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (v2)

Borislav Petkov wrote:
> On Thu, May 24, 2012 at 10:10:34AM +0000, Liu, Jinsong wrote:
>>>> Signed-off-by: Liu, Jinsong <jinsong.liu@...el.com>
>>>> Signed-off-by: Ke, Liping <liping.ke@...el.com>
>>>> Signed-off-by: Jiang, Yunhong <yunhong.jiang@...el.com>
>>>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
>>> 
>>> If you're sending the patch, you need to be the last on the
>>> SOB-chain and the SOB-chain has to show the proper path the patch
>>> took. See <Documentation/SubmittingPatches>.
> 
>> Thanks! I will update it. But I'm not quite clear 'the SOB-chain has
>> to show the proper path the patch took', would you elaborate more?
> 
> Section 12 in the SubmittingPatches readme has more or less an example
> about it, here's what I mean:
> 
> Signed-off-by: Initial Patch Author <ipa@...mple.com>
> Signed-off-by: Second Patch Author <spa@...mple.com>
> Signed-off-by: Third Patch Author <tpa@...mple.com>
> ...
> Signed-off-by: Patch Submitter <ps@...mple.com>
> 
> Some of the lines above may or may not be present depending on your
> case. If you're sending the patch, you're the last in chain so your
> SOB should be last.
> 
> That's what I mean with "proper path" the patch took, i.e. the SOB
> chain should show how exactly this patch was created and who handled
> it on its way upstream.
> 

Oh, I see your meaning now. Thanks for telling me kernel habit / culture about SOB. I will update accordingly.

> 
>>>> -static struct miscdevice mce_chrdev_device = {
>>>> +struct miscdevice mce_chrdev_device = {
>>>>  	MISC_MCELOG_MINOR,
>>>>  	"mcelog",
>>>>  	&mce_chrdev_ops,
>>> 
>>> You're still reusing those - pls, define your own 'struct miscdevice
>>> mce_chrdev_device' in drivers/xen/ or somewhere convenient and
>>> your own mce_chrdev_ops. The only thing you should be touching in
>>> arch/x86/.../mcheck/ is the export of MISC_MCELOG_MINOR.
>>> 
>>> Thanks.
>> 
>> I'm *not* reuse native code.
>> I have defined 'struct miscdevice xen_mce_chrdev_device' in
>> drivers/xen, and I also implement xen_mce_chrdev_ops, they are all
>> xen-self-contained.  
>> 
>> The patch just redirect native mce_chrdev_device to
>> xen_mce_chrdev_device when running under xen environment. 
>> It didn't change any native code (except just cancel
>> mce_chrdev_device 'static'), and will not break native logic. 
> 
> Why are you doing that?
> 
> Why don't you do
> 
> 	misc_register(&xen_mce_chrdev_device);
> 
> in xen_early_init_mcelog() ?
> 
> This way there'll be no arch/x86/ dependencies at all.

The reason is, if we do so, it would be covered by native misc_register(&mce_chrdev_device) later when native kernel init (xen init first and then start native kernel).
Under such case, if linux running under xen platform, /dev/mcelog point to vcpu, that's pointless since it cannot get any mcelog from physical cpu (which owned by xen).

Yes, we can use another misc device like /dev/xen-mcelog, w/ another device minor like 226, but that's not good for userspace mcelog tools. As far as I know, Novell mcelog use unified /dev/mcelog interface for linux running under either bare metal or xen platform.

This patch just do redirection at xen code path, and that would not hurt anything to native kernel.

Thanks,
Jinsong


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