Welcome To openEuler Community

Hey @huang-donghua-warehouse_admin , 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: Kernel ,
and any of the maintainers: @hanjunguo, @oekernel, @sanglipeng, @zeng_zhaorong, @zhengzengkai ,
and any of the committers: @CTC-XiboWang, @Frank_Sae, @GongLei-, @LiuYongQiang0816, @SuperSix173, @Tankll2021, @TrueAI, @allen-shi, @baratta, @caixu-blue, @chenjiesong, @chenjunxin1992, @chenke2026, @chiqijun, @chriszjh, @duanqiangwen, @fangfeng123, @fanghaiqinghw, @gaojuxin09, @gouhao2022, @guzitao, @hanjunguo, @hanliyang, @hellotcc, @hjx_gitff, @hongwu-wang, @htforge, @hu-chunzhi, @hunan4222, @jackknight, @jerry_lilijun, @junlong-zheng, @juntianlinux, @kailiu42, @kaitiandu, @kazero00, @kevinzhu1, @kile2009, @koishimind, @kongzizaixian, @leoliu-oc, @li-huisong, @linan888, @linyunsheng, @liulongfang, @lostway1, @lujialin2, @markyuan4ta21, @mingqian218472, @mufengyan, @qinirao, @robinorg, @rock_hw, @sanglipeng, @shu-shengming, @shuaijiakun, @sming56_admin, @stavewu, @stkid, @wangboe2022, @wenzhiwei11, @whoisxxx, @wkfxxx, @woqidaideshi, @wsoydl, @xingmz1, @xukuohai, @yeweihua999, @ygn-ndwd-official, @yonghu_4dc5, @young-sun, @yuehaibing_planb, @yuzenghui1, @zhang-changzhong, @zhangyi089, @zhujianwei001, @zichengqu, @zqiao216 .

@
issue变更为 [已取消/已挂起] 状态前，请操作者填写相关原因
请按如下格式评论原因后，重新进行操作

/reason xxxxxx

@allen-shi , @alvin-ling , @baratta , @caixu-blue , @chenguangli , @chenjiesong , @chenjunxin1992 , @chenke2026 , @chenwei_kernel , @chiqijun , @chriszjh , @colyli , @CTC-XiboWang , @duanqiangwen , @fangfeng123 , @fanghaiqinghw , @Frank_Sae , @gaojuxin09 , @georgeguo , @giree2 , @GongLei- , @gouhao2022 , @guohaocs2c , @guzitao , @hailan94 , @hanjunguo , @hanliyang , @haochengxie , @hellotcc , @hitmoon , @hjx_gitff , @hongwu-wang , @htforge , @hu-chunzhi , @hunan4222 , @jackknight , @jentlestea , @jerry_lilijun , @jiaoff , @junlong-zheng , @juntianlinux , @kailiu42 , @kaitiandu , @kazero00 , @kevinzhu1 , @kile2009 , @koishimind , @kongzizaixian , @kylin-mayukun , @lengchao , @leoliu-oc , @liaotao-wave , @li-huisong , @linan888 , @lindv , @linyunsheng , @liulongfang , @LiuYongQiang0816 , @lixuefeng-loongson , @LiYihang226 , @lostway1 , @lujialin2 , @maobibo , @mao-hongbo , @markyuan4ta21 , @mingqian218472 , @mufengyan , @newbeats , @pi3orama , @qinirao , @robinorg , @rock_hw , @sanglipeng , @shuaijiakun , @shu-shengming , @sming56_admin , @stavewu , @stkid , @sunying2022 , @SuperSix173 , @Tankll2021 , @TrueAI , @wangboe2022 , @wangxiongfeng , @wenzhiwei11 , @whoisxxx , @wkfxxx , @woqidaideshi , @wsoydl , @xingmz1 , @xukuohai , @yeweihua999 , @ygn-ndwd-official , @yonghu_4dc5 , @young1c , @young-sun , @yuehaibing_planb , @yuzenghui1 , @zhang-changzhong , @zhangwei123171 , @zhangyi089 , @zhenpengzheng , @zhujianwei001 , @zichengqu , @zqiao216
以下的要求不是强制性的, 未按模板评论时对issue无任何影响
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, 缺陷严重等级, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后defect-manager将无法正常解析填写内容.
评论区可能使用到的指令说明:

影响性分析说明:

缺陷严重等级:(Critical/High/Moderate/Low)

缺陷根因说明:

受影响版本排查(受影响/不受影响):

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

abi变化(是/否):

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

缺陷issue处理具体操作请参考:
https://gitcode.com/Coopermassaki/cve-manager/blob/master/cve-vulner-manager/doc/md/defect-manager-manual.md
pr关联issue具体操作请参考:
https://docs.gitcode.com/docs/help/home/org_project/pullrequests/pr-related-issue

@ 未对受影响版本排查/abi变化进行分析

@ 未对受影响版本排查/abi变化进行分析