[sync] PR-201: libmultipath: limit paths that can get wwid from environment · Pull Request !202 · src-openEuler/multipath-tools

### 1. Origin pull request:
https://gitee.com/src-openeuler/multipath-tools/pulls/201

### 2. Original pull request related issue(s):
https://gitee.com/src-openeuler/multipath-tools/issues/IAIQ7C

### 3. Original pull request related commit(s):
| Sha | Datetime | Message |
|---|---|---|
|[07e08e42](https://gitee.com/src-openeuler/multipath-tools/commits/07e08e42400b8c37b2dacdc63e8ea4c737cc11b3)|2024-08-08 14:47:28 +0800 CST|libmultipath: limit paths that can get wwid from environment Currently, whenever getting the uid_attribute from the udev database fails, multipath will try to get it from the environment variables. This normally isn't a problem, since either multipath -u is getting called from a uevent and the environment will have the correct value in that variable, or something else is being run and that variable won't be set. However, when find_multipaths is configured to "smart", this causes problems. For maybe devices, multipath needs to get the WWIDs of all the other block devices, to see if they match the maybe device wwid. If one of those devices doesn't have uid_attribute set in its udev database, multipath will fall back to checking the environment for it, and it will find that variable set to the WWID of the maybe device that this uevent is for. This means that all devices with no WWID will end up appearing to have the same WWID as the maybe device, causing multipath to incorrectly claim it. |

src-openEuler/multipath-tools .gitee-modal { width: 500px !important; }

搜索帮助

src-openEuler/multipath-tools