登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
Gitee 年度开源项目评选中~
代码拉取完成,页面将自动刷新
仓库状态说明
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
7
Star
0
Fork
48
src-openEuler
/
sssd
关闭
代码
Issues
0
Pull Requests
0
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
回合上游社区补丁,补丁数量:5
已完成
#I92WCZ
缺陷
peulerosci
创建于
2024-02-22 14:44
<p>需要同步的补丁如下:</p><p></p><table ><tr><td colSpan="1" rowSpan="1">CommitId</td><td colSpan="1" rowSpan="1">描述</td></tr><tr><td colSpan="1" rowSpan="1">230e7757a7805c7c530d0914936f353882bd504e</td><td colSpan="1" rowSpan="1">LOGROTATE: logrotate should also signal sssd_kcm<br/><br/>sssd_kcm is not registered with SSSD's monitor, so it is not signaled<br/>when it must restart the log. Adding this command will directly signal<br/>sssd_kcm (in addition to the monitor).<br/><br/>If sssd_kcm is also running in one or more containers, they will also<br/>receive the signal. Because only the log files in the host where rotated,<br/>the instances in the containers will go on using the same log files.<br/>Nothing will happen except for the Received SIGHUP. Rotating logfiles.<br/>message in the log files. If we want to avoid this, we should implement<br/>a PID file.<br/><br/>Reviewed-by: Sumit Bose <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">3cba6d1153c102f9596335db28cc017e8338e868</td><td colSpan="1" rowSpan="1">KCM: Fixed a wrong check<br/><br/>The pointer to the newly allocated iobuffer is stored into<br/>state->op_ctx->reply but the check for NULL is done on state->reply,<br/>which we already know is not NULL because it was checked before and<br/>not modified after that.<br/><br/>Reviewed-by: Alexey Tikhonov <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">ae6b9163be0a5a8846e8dbf2e0da2c29221781b9</td><td colSpan="1" rowSpan="1">pam_sss: fix passthrow of old authtok from another pam modules at PAM_PRELIM_CHECK<br/><br/>pam_sss ignored old authtoks passed from another pam modules<br/><br/>Resolves: https://github.com/SSSD/sssd/issues/7007<br/>Resolves: https://github.com/SSSD/sssd/issues/5418<br/><br/>Reviewed-by: Iker Pedrosa <br/>Reviewed-by: Sumit Bose </td></tr><tr><td colSpan="1" rowSpan="1">cffe6e09c6b4cd8afa049365bbd432ace5d2a9d9</td><td colSpan="1" rowSpan="1">nssidmap: fix sss_nss_getgrouplist_timeout() with empty secondary group list<br/><br/>sss_nss_getgrouplist_timeout() is intended as a replacement for<br/>getgrouplist() which only gets secondary groups from SSSD. Currently it<br/>returns an ENOENT error if there are no secondary groups returned by<br/>SSSD. However, as with getgrouplist(), there is the second parameter<br/>which expects a single GID which will be added to the result. This means<br/>that sss_nss_getgrouplist_timeout() will always return at least this GID<br/>as a result and an ENOENT error does not make sense.<br/><br/>With this patch sss_nss_getgrouplist_timeout() will not return an error<br/>anymore if there are no secondary groups but just a result with the<br/>single GID from the second parameter.<br/><br/>Reviewed-by: Alejandro López <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">cbae6855320b53f3f2bdc0e11c5a9c8eb84daf87</td><td colSpan="1" rowSpan="1">KCM: Fix a memory leak<br/><br/>When an operation is processed, a buffer is allocated for the reply<br/>and its parent is the client context (struct cli_ctx). This buffer<br/>is not explicitly freed but it is released when the client context is<br/>freed. With each operation a new buffer is allocated and the<br/>previous one gets lost.<br/><br/>This is not an actual leak because the lost buffers are released by<br/>talloc once the client context is freed, when the connection is closed.<br/>But on long-lived connections this can consume a large amount of memory<br/>before the connection is closed.<br/><br/>To solve this, the request context (struct kcm_req_ctx) is the new<br/>parent of the buffer. The request is freed as soon as the operation is<br/>completed and no buffer gets lost.<br/><br/>Resolves: https://github.com/SSSD/sssd/issues/7072<br/><br/>Reviewed-by: Iker Pedrosa <br/>Reviewed-by: Sumit Bose </td></tr></table><p></p>
<p>需要同步的补丁如下:</p><p></p><table ><tr><td colSpan="1" rowSpan="1">CommitId</td><td colSpan="1" rowSpan="1">描述</td></tr><tr><td colSpan="1" rowSpan="1">230e7757a7805c7c530d0914936f353882bd504e</td><td colSpan="1" rowSpan="1">LOGROTATE: logrotate should also signal sssd_kcm<br/><br/>sssd_kcm is not registered with SSSD's monitor, so it is not signaled<br/>when it must restart the log. Adding this command will directly signal<br/>sssd_kcm (in addition to the monitor).<br/><br/>If sssd_kcm is also running in one or more containers, they will also<br/>receive the signal. Because only the log files in the host where rotated,<br/>the instances in the containers will go on using the same log files.<br/>Nothing will happen except for the Received SIGHUP. Rotating logfiles.<br/>message in the log files. If we want to avoid this, we should implement<br/>a PID file.<br/><br/>Reviewed-by: Sumit Bose <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">3cba6d1153c102f9596335db28cc017e8338e868</td><td colSpan="1" rowSpan="1">KCM: Fixed a wrong check<br/><br/>The pointer to the newly allocated iobuffer is stored into<br/>state->op_ctx->reply but the check for NULL is done on state->reply,<br/>which we already know is not NULL because it was checked before and<br/>not modified after that.<br/><br/>Reviewed-by: Alexey Tikhonov <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">ae6b9163be0a5a8846e8dbf2e0da2c29221781b9</td><td colSpan="1" rowSpan="1">pam_sss: fix passthrow of old authtok from another pam modules at PAM_PRELIM_CHECK<br/><br/>pam_sss ignored old authtoks passed from another pam modules<br/><br/>Resolves: https://github.com/SSSD/sssd/issues/7007<br/>Resolves: https://github.com/SSSD/sssd/issues/5418<br/><br/>Reviewed-by: Iker Pedrosa <br/>Reviewed-by: Sumit Bose </td></tr><tr><td colSpan="1" rowSpan="1">cffe6e09c6b4cd8afa049365bbd432ace5d2a9d9</td><td colSpan="1" rowSpan="1">nssidmap: fix sss_nss_getgrouplist_timeout() with empty secondary group list<br/><br/>sss_nss_getgrouplist_timeout() is intended as a replacement for<br/>getgrouplist() which only gets secondary groups from SSSD. Currently it<br/>returns an ENOENT error if there are no secondary groups returned by<br/>SSSD. However, as with getgrouplist(), there is the second parameter<br/>which expects a single GID which will be added to the result. This means<br/>that sss_nss_getgrouplist_timeout() will always return at least this GID<br/>as a result and an ENOENT error does not make sense.<br/><br/>With this patch sss_nss_getgrouplist_timeout() will not return an error<br/>anymore if there are no secondary groups but just a result with the<br/>single GID from the second parameter.<br/><br/>Reviewed-by: Alejandro López <br/>Reviewed-by: Tomáš Halman </td></tr><tr><td colSpan="1" rowSpan="1">cbae6855320b53f3f2bdc0e11c5a9c8eb84daf87</td><td colSpan="1" rowSpan="1">KCM: Fix a memory leak<br/><br/>When an operation is processed, a buffer is allocated for the reply<br/>and its parent is the client context (struct cli_ctx). This buffer<br/>is not explicitly freed but it is released when the client context is<br/>freed. With each operation a new buffer is allocated and the<br/>previous one gets lost.<br/><br/>This is not an actual leak because the lost buffers are released by<br/>talloc once the client context is freed, when the connection is closed.<br/>But on long-lived connections this can consume a large amount of memory<br/>before the connection is closed.<br/><br/>To solve this, the request context (struct kcm_req_ctx) is the new<br/>parent of the buffer. The request is freed as soon as the operation is<br/>completed and no buffer gets lost.<br/><br/>Resolves: https://github.com/SSSD/sssd/issues/7072<br/><br/>Reviewed-by: Iker Pedrosa <br/>Reviewed-by: Sumit Bose </td></tr></table><p></p>
评论 (
2
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
修复中
已确认
已完成
已验收
已取消
负责人
未设置
hzero1996
hzero1996
负责人
协作者
+负责人
+协作者
标签
sig/Base-service
未设置
项目
未立项任务
未立项任务
里程碑
未关联里程碑
未关联里程碑
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (29)
标签 (35)
master
openEuler-22.03-LTS-SP3
openEuler-20.03-LTS-SP4
openEuler-22.03-LTS-SP4
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS-SP3
openEuler-24.03-LTS-Next
openEuler-24.03-LTS
openEuler-25.09
openEuler-22.03-LTS-SP2
openEuler-24.09
openEuler-25.03
openEuler-22.03-LTS-SP1
openEuler-20.03-LTS-SP1
openEuler-22.03-LTS
openEuler-22.03-LTS-Next
openEuler-20.03-LTS-SP3
openEuler-23.09
openEuler-23.03
openEuler-22.09
openEuler-21.09
openEuler-20.03-LTS
openEuler-20.03-LTS-Next
openEuler-20.03-LTS-SP2
openEuler-21.03
openEuler-20.09
openEuler1.0
openEuler1.0-base
openEuler-24.03-LTS-SP1-update-20251024
openEuler-20.03-LTS-SP4-update-20251024
openEuler-22.03-LTS-SP3-update-20251024
openEuler-24.03-LTS-update-20251024
openEuler-22.03-LTS-SP4-update-20251024
openEuler-25.09-release
openEuler-20.03-LTS-SP4-update-20250919
openEuler-22.03-LTS-SP3-update-20250919
openEuler-24.03-LTS-update-20250919
openEuler-22.03-LTS-SP4-update-20250919
openEuler-24.03-LTS-SP1-update-20250919
openEuler-24.03-LTS-SP2-update-20250919
openEuler-24.03-LTS-SP2-release
openEuler-25.03-release
openEuler-24.03-LTS-SP1-release
openEuler-22.03-LTS-SP4-release
openEuler-24.09-release
openEuler-24.03-LTS-release
openEuler-22.03-LTS-SP3-release
openEuler-23.09-rc5
openEuler-22.03-LTS-SP1-release
openEuler-22.09-release
openEuler-22.09-rc5
openEuler-22.09-20220829
openEuler-22.03-LTS-20220331
openEuler-22.03-LTS-round5
openEuler-22.03-LTS-round3
openEuler-22.03-LTS-round2
openEuler-22.03-LTS-round1
openEuler-20.03-LTS-SP3-release
openEuler-20.03-LTS-SP2-20210624
openEuler-21.03-20210330
openEuler-20.09-20200929
openEuler-20.03-LTS-20200606
openEuler-20.03-LTS-tag
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
预计工期
(小时)
参与者(1)
1
https://gitee.com/src-openeuler/sssd.git
git@gitee.com:src-openeuler/sssd.git
src-openeuler
sssd
sssd
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册