Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Donate
Please sign in before you donate.
Cancel
Sign in
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
Watch
Unwatch
Watching
Releases Only
Ignoring
7
Star
0
Fork
47
src-openEuler
/
sssd
Closed
Code
Issues
0
Pull Requests
0
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
回合上游社区补丁,补丁数量:5
Done
#I92WCZ
Bug
peulerosci
Opened this issue
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>
Comments (
2
)
Sign in
to comment
Status
Done
Backlog
已挂起
Fixing
Confirmed
Done
Accepted
Canceled
Assignees
Not set
hzero1996
hzero1996
Assignee
Collaborator
+Assign
+Mention
Labels
sig/Base-service
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(2)
1
https://gitee.com/src-openeuler/sssd.git
git@gitee.com:src-openeuler/sssd.git
src-openeuler
sssd
sssd
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register