# Re: \[PATCH v25 10/21\] x86/sgx: Linux Enclave Driver

- From: Haitao Huang \<hidden\>
- Date: 2020-02-05 15:58:20 
- List: linux-security-module
- Page: https://ratatoskr.run/linux-security-module/2020/02/5852172
- Thread: https://ratatoskr.run/linux-security-module/2020/02/5850932/t.md

```text
On Tue, 04 Feb 2020 00:05:34 -0600, Jarkko Sakkinen [ref] 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
```
