rsyslog社区补丁定期回合

<h3>优先级:</h3>次要<h3>详细描述:</h3> 【OS版本】：被测的版本信息openEuler-2023-11-21-00-12-20 【测试类型】：发现问题的测试类型，功能测试、可靠性测试、性能测试等 【测试步骤】：详细描述可以复现该问题的测试步骤经分析rsyslog需要合入以下社区补丁：<table ><tr><td colSpan="1" rowSpan="1">包名</td><td colSpan="1" rowSpan="1">commit Url</td><td colSpan="1" rowSpan="1">补丁名</td><td colSpan="1" rowSpan="1">来源</td><td colSpan="1" rowSpan="1">补丁提交时间</td><td colSpan="1" rowSpan="1">补丁类型</td><td colSpan="1" rowSpan="1">影响分析</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/b73ccfb4be883862f1405bd40deca5a111f0c0a2</td><td colSpan="1" rowSpan="1">tcp-net-subsystem-handle-data-race-gracefully</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-10-02 15:32:07</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">在设置poll()或在系统调用内部时，套接字文件描述符可能已关闭。这以前被视为错误，并在调试生成中导致中止。这一点现在已经得到了解决，现在可以优雅地忽略它。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/144cc03d90293cc09c4c100dd941226b421709e2</td><td colSpan="1" rowSpan="1">fix-startup-issue-on-modern-systemd-systems</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-09-28 20:11:31</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复当rsyslog自动后台运行时，若打开的文件描述符fd过多会导致rsyslog.service启动失败并报错&#x27;rsyslog startup failure, child did not respond within startup timeout&#x27;问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/c8a2969580935121440f220af03d74ab1dfa5c11</td><td colSpan="1" rowSpan="1">tcpflood-bugfix-plain-tcp-send-error-not-properly-reported</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-09-13 15:33:40</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复sendPlainTCP()未正确返回tcp发送失败时的错误代码，导致没有任何有意义的错误消息的问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/8d36cbd29d8db7091e13dd8d720b744c7399acf2</td><td colSpan="1" rowSpan="1">lookup-tables-fix-static-analyzer-issue</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-08-02 21:02:05</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">当rsyslog 收到信号“HUP”且未重新加载lookup_table时，则不会设置查找表的名称。这可能导致NULL指针访问。通过该补丁修复这个问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/b6b4f25eda025d3f5a5fcbf2be395bfade03d788</td><td colSpan="1" rowSpan="1">lookup-tables-bugfix-reload-on-HUP-did-not-work-when-backgrounded</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-08-02 21:01:31</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复在以“forked”模式（不带 -n 选项）运行rsyslog的场景下，当 rsyslog 收到信号“HUP”时，未按照预期重新加载lookup_table的问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/8d8fe80d871b07ab14f44e4fddb68445601b66b5</td><td colSpan="1" rowSpan="1">openssl-Replaced-depreceated-method-SSLv23_method-with-TLS_method</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-07-28 22:27:07</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">在 OpenSSL 1.1.0 及更高版本中，SSLv23_method有时会导致 TLS 握手出现一些错误。由于此方法自 1.1.0 起已被弃用，因此应该将其替换为后续方法TLS_method。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/0e5444706dfbec105a15414210013c535766e04f</td><td colSpan="1" rowSpan="1">testbench-make-waiting-for-HUP-processing-more-reliable</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-07-26 23:17:01</td><td colSpan="1" rowSpan="1">TestCode</td><td colSpan="1" rowSpan="1">测试用例代码，新增await_HUP_processed()函数，以替换测试用例中通过sleep来实现的HUP处理，可以加快测试用例的运行速度。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/f2bac98f2ada404fb8ed9bc10ff13bfb72366abd</td><td colSpan="1" rowSpan="1">mmnormalize-bugfix-if-msg-cannot-be-parsed-parser-chain-is-stopped</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-06-16 21:40:02</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复在无法解析消息的情况下，解析器链将停止的问题。  当解析器无法解析消息时，它应该向 rsyslog 核心指示这一点，然后 rsyslog 核心会激活配置的解析器链内的下一个解析器。不幸的是，mmnormalize 总是告诉核心“成功”，因此没有其他解析器被激活。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/1dfa5f9d836d2153fb76bcbbb235cf5bfdff538b</td><td colSpan="1" rowSpan="1">core-bugfix-potential-segfault-on-busy-systems</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2023-06-06 20:17:28</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复因条件竞争而导致的segfault问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/fcf72d6ac5662e3cee536eddbae1b4fa9f1aff8a</td><td colSpan="1" rowSpan="1">imfile-fix-ext-directory-s-fd-leak-in-case-of-inotify-on-symlink</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2022-12-05 13:36:19</td><td colSpan="1" rowSpan="1">BugFix</td><td colSpan="1" rowSpan="1">修复imfile模块中的外部目录 fd 泄漏问题。</td></tr><tr><td colSpan="1" rowSpan="1">rsyslog</td><td colSpan="1" rowSpan="1">https://github.com/rsyslog/rsyslog/commit/e8ac82e09f930bf99421cc323c24a9dbf215f9da</td><td colSpan="1" rowSpan="1">imfile-tests-ext-directory-s-fd-leak-in-case-of-inotify-on-symlink</td><td colSpan="1" rowSpan="1">开源</td><td colSpan="1" rowSpan="1">2022-12-05 13:35:33</td><td colSpan="1" rowSpan="1">TestCode</td><td colSpan="1" rowSpan="1">新增测试用例，用于测试是否会发生外部目录 fd 泄漏。</td></tr></table> 【结果输出】：根据上述测试步骤执行后，系统的实际输出社区补丁未合入 【预期输出】：系统在上述测试步骤操作后，按照系统设计应该输出的结果回合社区补丁 【测试代码】：发现问题的测试代码，或者关键片段，能指导问题复现 【初步定位结论】：已明确的相关定位信息或者相关的沟通交流信息 <h3>原因分析:</h3>【是否新引入rpm包，是否进行了安全编译选项扫描】不涉及【定位分析】【对外部是否有影响】不涉及

src-openEuler/rsyslog
关闭

内容风险标识

评论 (1)

src-openEuler/rsyslog关闭 .gitee-modal { width: 500px !important; }

内容风险标识