Re: [PATCH] nvme-multipath: fix sysfs dangerously created links

2018-02-27 1:24 GMT+09:00 Keith Busch : > On Mon, Feb 26, 2018 at 05:51:23PM +0900, baeg...@gmail.com wrote: >> From: Baegjae Sung >> >> If multipathing is enabled, each NVMe subsystem creates a head >> namespace (e.g., nvme0n1) and multiple private namespaces >> (e.g., nvme0c0n1 and nvme0c1n1) in

Re: [PATCH] nvme-multipath: fix sysfs dangerously created links

On Mon, Feb 26, 2018 at 05:51:23PM +0900, baeg...@gmail.com wrote: > From: Baegjae Sung > > If multipathing is enabled, each NVMe subsystem creates a head > namespace (e.g., nvme0n1) and multiple private namespaces > (e.g., nvme0c0n1 and nvme0c1n1) in sysfs. When creating links for > private name

[PATCH] nvme-multipath: fix sysfs dangerously created links

From: Baegjae Sung If multipathing is enabled, each NVMe subsystem creates a head namespace (e.g., nvme0n1) and multiple private namespaces (e.g., nvme0c0n1 and nvme0c1n1) in sysfs. When creating links for private namespaces, links of head namespace are used, so the namespace creation order must