Pull Request已成功合入, 合并人@openeuler-ci-bot
（感谢 kouwq 的贡献）
Welcome To openEuler Community
Hey @kouwq , thanks for your contribution to the community.
Bot Usage Manual
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.
Contact Guide
If you have any questions, please contact the SIG: Storage ,
and any of the maintainers: @VICTORY2017, @dragon1147e3, @kouwq, @liuzhiqiang26, @louhongxiang, @mszjaas, @swf504 ,
and any of the committers: @foolstrong, @kouwq .
当前仓库存在以下 保护分支 ：
| Protected Branch | Version | Release |
|---|---|---|
| master | 0.9.5 | 18 |
| openEuler-26.09-DevStation | 0.9.5 | 18 |
| openEuler-26.09 | 0.9.5 | 18 |
| openEuler-20.03-LTS-SP4 | 0.8.4 | 44 |
| openEuler-22.03-LTS-SP4 | 0.8.7 | 26 |
| openEuler-24.03-LTS-Next | 0.9.5 | 18 |
| openEuler-24.03-LTS-SP3 | 0.9.5 | 18 |
| openEuler-24.03-LTS-SP1 | 0.9.5 | 18 |
| openEuler-24.03-LTS-SP4 | 0.9.5 | 18 |
| openEuler1.0-base | 0.7.7 | 15 |
| openEuler1.0 | 0.7.7 | 15 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支（创建同步 PR）：
a) 如果当前 PR 是 Open 状态，同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged，将立即执行同步操作
注意：
- /sync 命令可以指定同步到多个分支，仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确，可通过向同步 PR 的源分支提交轻量级 PR 完善，或使用 /close 命令关闭
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/multipath-tools/42/console
aarch64架构构建及构建后检查：multiarch/src-openeuler/aarch64/multipath-tools/42/console
x86_64架构构建及构建后检查：multiarch/src-openeuler/x86-64/multipath-tools/42/console
| Check Name | Build Result | 详情 | Build Details | |
|---|---|---|---|---|
| check_binary_file | ✅SUCCESS | #42 | ||
| check_lfsconfig | :ballot_box_with_check:EXCLUDE | |||
| check_package_yaml_file | ✅SUCCESS | |||
| check_repo_in_maintain | ✅SUCCESS | |||
| check_consistency | ✅SUCCESS | |||
| check_spec_file | ✅SUCCESS | |||
| x86_64 | check_build | ✅SUCCESS | #42 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||
| aarch64 | check_build | ✅SUCCESS | #42 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||
如下为接口变更检查结果，目标分支为openEuler-20.03-LTS-SP4，请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | ✅SUCCESS | #42 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | ✅SUCCESS | |||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS | |||
| rpm_service | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS | |||
| compare_package(aarch64) | add_rpms | ✅SUCCESS | #42 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | ✅SUCCESS | |||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS | |||
| rpm_service | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS |
/lgtm
/approve
当前PR是否有AI参与: x
[x] 否
[ ] Yes
__1. AI Agent 平台:
__2. AI 模型 :
__3. Prompt 上下文 :
参考：openEuler社区《生成式AI工具使用与开源贡献政策》
PR功能描述 / 为什么需要这个合入**:
kpartx命令指定的-p参数过长时，会导致kpartx进程coredump
原因是kpartx.c的ADD/UPDATE分区处理循环中局部变量part_uuid声明时未初始化为NULL，当-p 参数过长导致format_partname函数构造分区名称失败时，dm_find_part提前返回但未设置输出参数*part_uuid，调用者未区分"未找到分区"和"名称构造失败"两种返回0的场景，直接使用未初始化的part_uuid指针调用check_uuid → strchr
移植上游社区补丁修复该问题：
https://github.com/openSUSE/multipath-tools/commit/f474bdf9d016e580baea54f1c3d7282b6623ffdd
https://github.com/openSUSE/multipath-tools/commit/030710318a9d991724cdb908c8519702cd9cbc35
https://github.com/openSUSE/multipath-tools/commit/eedf032d0c5ca3b4adc5c75863270d82f6b41e15
该PR关联的issue
(格式为fixes #<issue号>, 或者resolves #<issue号>): fixes #
fix #76
希望检视人员了解: