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: <op.0fiundhawjvjmi@hhuan26-mobl1.amr.corp.intel.com>
Date:   Wed, 05 Feb 2020 09:58:15 -0600
From:   "Haitao Huang" <haitao.huang@...ux.intel.com>
To:     linux-kernel@...r.kernel.org, x86@...nel.org,
        linux-sgx@...r.kernel.org,
        "Jarkko Sakkinen" <jarkko.sakkinen@...ux.intel.com>
Cc:     akpm@...ux-foundation.org, dave.hansen@...el.com,
        sean.j.christopherson@...el.com, nhorman@...hat.com,
        npmccallum@...hat.com, haitao.huang@...el.com,
        andriy.shevchenko@...ux.intel.com, tglx@...utronix.de,
        kai.svahn@...el.com, bp@...en8.de, josh@...htriplett.org,
        luto@...nel.org, kai.huang@...el.com, rientjes@...gle.com,
        cedric.xing@...el.com, puiterwijk@...hat.com,
        "Jarkko Sakkinen" <jarkko.sakkinen@...el.com>,
        linux-security-module@...r.kernel.org,
        "Suresh Siddha" <suresh.b.siddha@...el.com>
Subject: Re: [PATCH v25 10/21] x86/sgx: Linux Enclave Driver

On Tue, 04 Feb 2020 00:05:34 -0600, Jarkko Sakkinen  
<jarkko.sakkinen@...ux.intel.com> wrote:
...
> +const struct file_operations sgx_provision_fops = {
> +	.owner			= THIS_MODULE,
> +};
> +
> +static struct miscdevice sgx_dev_enclave = {
> +	.minor = MISC_DYNAMIC_MINOR,
> +	.name = "enclave",
> +	.nodename = "sgx/enclave",
> +	.fops = &sgx_encl_fops,
> +};
> +

How does kernel manage name conflict if multiple misc device requesting  
"enclave" ?

And the attributes for a udev rule to match this device according to  
udevadm output are:
SUBSYSTEM=="misc",KERNEL=="enclave"

Is that specific enough to uniquely match this device?

Similar questions for the "provision" device introduced later in this  
series.

Thanks
Haitao

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ