[PATCH v25 10/21] x86/sgx: Linux Enclave Driver
Haitao Huang
haitao.huang at linux.intel.com
Wed Feb 5 15:58:15 UTC 2020
On Tue, 04 Feb 2020 00:05:34 -0600, Jarkko Sakkinen
<jarkko.sakkinen at linux.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
More information about the Linux-security-module-archive
mailing list