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: <DE8DF0795D48FD4CA783C40EC82923351F10DE@SHSMSX101.ccr.corp.intel.com>
Date:	Fri, 25 May 2012 20:47:20 +0000
From:	"Liu, Jinsong" <jinsong.liu@...el.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC:	Borislav Petkov <bp@...64.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Luck, Tony" <tony.luck@...el.com>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>
Subject: RE: [Xen-devel] [PATCH 1/3] xen/mce: Add mcelog support for Xen
 platform (v2)

Konrad Rzeszutek Wilk wrote:
>> What I mean is,
>> If mcelog.c create /dev/xen-mcelog (say, minor=226), native mce.c
>> would create /dev/mcelog (minor=227). 
>> Under such case, may we create a symlink in /dev/mcelog pointing to
>> /dev/xen-mcelog, without touching native mce code? and how? 
> 
> I thought the idea was that we would create /dev/mcelog using the
> same major/minor. 

Our current patch just use same major/minor, by redirection method. Is it acceptable?

> 
> However if you want to create /dev/xen-mcelog and then create from
> the kernel another file in /dev that is name 'mcelog' and is a
> symlink to /dev/mcelog - that is OK too. Obviously you will also need
> to disable the generic '/dev/mcelog' (and that can be done in the
> same way as lguest does it). 

No, that's not my purpose.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ