登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
轻量养虾,开箱即用!低 Token + 稳定算力,Gitee & 模力方舟联合出品的 PocketClaw 正式开售!点击了解详情
代码拉取完成,页面将自动刷新
仓库状态说明
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
128
Star
73
Fork
329
src-openEuler
/
kernel
关闭
代码
Issues
1197
Pull Requests
35
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
开发画像分析
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
[openEuler-20.03-LTS-SP3]打开kmemleak开关重编内核,重启后扫描到内存泄漏
已完成
#I8FDPC
缺陷
songmengxue
创建于
2023-11-10 11:10
**【标题描述】x86/arm打开kmemleak开关重编内核,重启后扫描到内存泄漏 **【环境信息】** 硬件信息: 虚机场景提供虚机XML文件 虚拟机规格:8cpu + 8G内存 + 100G存储 arm使用鲲鹏物理机装虚拟机, 虚拟机CPU模式为host-passthrough x86使用intel物理机装虚拟机,虚拟机CPU模式为host-passthrough 软件信息: 1)系统版本:openEuler 20.03 LTS SP3 2)内核版本:4.19.90-2112.8.0.0131.oe1.aarch64 **【问题复现步骤】** 1.安装虚拟机 2.按照官方文档打开kmemleak开关重新编译内核,安装新内核重启(参照官方文档https://forum.openeuler.org/t/topic/615/1) [root@wsip-70-182-148-86 ~]# cat /boot/config-4.19.91 | grep -i kmemleak CONFIG_HAVE_DEBUG_KMEMLEAK=y CONFIG_DEBUG_KMEMLEAK=y CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=40000 #CONFIG_DEBUG_KMEMLEAK_TEST is not set #CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set 3.查看/sys/kernel/debug/kmemleak文件扫描到selinux disabled前后内存泄漏 **【预期结果】** 没有内存泄漏 **【实际结果】** 查看/sys/kernel/debug/kmemleak文件扫描到selinux disabled前后内存泄漏 **【其他相关附件信息】** 查看/var/log/message日志 [root@wsip-70-182-148-86 ~]# cat /var/log/messages | grep kmemleak Nov 9 20:37:36 localhost kernel: [ 2.848656] kmemleak: Kernel memory leak detector initialized Nov 9 20:37:36 localhost kernel: [ 2.848663] kmemleak: Automatic memory scanning thread started Nov 9 20:48:51 localhost kernel: [ 677.872302] kmemleak: 164 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 20:58:57 localhost kernel: [ 1284.084692] kmemleak: 39 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 21:09:03 localhost kernel: [ 1890.282490] kmemleak: 12 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 21:39:22 localhost kernel: [ 3708.957539] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:09:41 localhost kernel: [ 5527.552732] kmemleak: 6 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:19:47 localhost kernel: [ 6133.739624] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:29:53 localhost kernel: [ 6739.944560] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 23:00:12 localhost kernel: [ 8558.524334] kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:00:49 localhost kernel: [12195.705164] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:31:08 localhost kernel: [14014.290435] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:41:14 localhost kernel: [14620.492264] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 02:22:16 localhost kernel: [20682.452430] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 10:07:01 localhost kernel: [48567.471949] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 10:24:23 localhost kernel: [ 2.814167] kmemleak: Kernel memory leak detector initialized Nov 10 10:24:23 localhost kernel: [ 2.814169] kmemleak: Automatic memory scanning thread started 查看/sys/kernel/debug/kmemleak日志 [root@wsip-70-182-148-86 ~]#cat /sys/kernel/debug/kmemleak | wc -l 4706 [root@wsip-70-182-148-86 ~]#cat /sys/kernel/debug/kmemleak unreferenced object 0xffff8000e1dce080 (size 128): comm "swapper/0", pid 1, jiffies 4294892835 (age 684.748s) hex dump (first 32 bytes): 00 70 ec e2 00 80 ff ff 03 00 00 00 05 00 00 00 .p.............. 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000f2295178>] kmem_cache_alloc_trace+0x138/0x230 [<00000000fe5aa91d>] selinux_sb_alloc_security+0x30/0x98 [<00000000345b4d79>] security_sb_alloc+0x30/0x50 [<00000000ab4bc082>] sget_userns+0x16c/0x4c8 [<00000000832e6498>] sget+0x88/0xb8 [<00000000bd79c97f>] mount_single+0x48/0xd8 [<000000005caf29b9>] sel_mount+0x3c/0x50 [<00000000b6f4d911>] mount_fs+0x50/0x280 [<000000003eff9f49>] vfs_kern_mount.part.10+0x54/0x188 [<000000008cdafa20>] kern_mount_data+0x38/0x58 [<000000005e17d84c>] init_sel_fs+0xa4/0x138 [<00000000e7d478c1>] do_one_initcall+0x54/0x220 [<0000000019ba2fa5>] kernel_init_freeable+0x2b0/0x3a0 [<000000008d87871a>] kernel_init+0x18/0x118 [<00000000aba7c0d0>] ret_from_fork+0x10/0x18 [<00000000213be9f5>] 0xffffffffffffffff
**【标题描述】x86/arm打开kmemleak开关重编内核,重启后扫描到内存泄漏 **【环境信息】** 硬件信息: 虚机场景提供虚机XML文件 虚拟机规格:8cpu + 8G内存 + 100G存储 arm使用鲲鹏物理机装虚拟机, 虚拟机CPU模式为host-passthrough x86使用intel物理机装虚拟机,虚拟机CPU模式为host-passthrough 软件信息: 1)系统版本:openEuler 20.03 LTS SP3 2)内核版本:4.19.90-2112.8.0.0131.oe1.aarch64 **【问题复现步骤】** 1.安装虚拟机 2.按照官方文档打开kmemleak开关重新编译内核,安装新内核重启(参照官方文档https://forum.openeuler.org/t/topic/615/1) [root@wsip-70-182-148-86 ~]# cat /boot/config-4.19.91 | grep -i kmemleak CONFIG_HAVE_DEBUG_KMEMLEAK=y CONFIG_DEBUG_KMEMLEAK=y CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=40000 #CONFIG_DEBUG_KMEMLEAK_TEST is not set #CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set 3.查看/sys/kernel/debug/kmemleak文件扫描到selinux disabled前后内存泄漏 **【预期结果】** 没有内存泄漏 **【实际结果】** 查看/sys/kernel/debug/kmemleak文件扫描到selinux disabled前后内存泄漏 **【其他相关附件信息】** 查看/var/log/message日志 [root@wsip-70-182-148-86 ~]# cat /var/log/messages | grep kmemleak Nov 9 20:37:36 localhost kernel: [ 2.848656] kmemleak: Kernel memory leak detector initialized Nov 9 20:37:36 localhost kernel: [ 2.848663] kmemleak: Automatic memory scanning thread started Nov 9 20:48:51 localhost kernel: [ 677.872302] kmemleak: 164 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 20:58:57 localhost kernel: [ 1284.084692] kmemleak: 39 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 21:09:03 localhost kernel: [ 1890.282490] kmemleak: 12 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 21:39:22 localhost kernel: [ 3708.957539] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:09:41 localhost kernel: [ 5527.552732] kmemleak: 6 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:19:47 localhost kernel: [ 6133.739624] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 22:29:53 localhost kernel: [ 6739.944560] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 9 23:00:12 localhost kernel: [ 8558.524334] kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:00:49 localhost kernel: [12195.705164] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:31:08 localhost kernel: [14014.290435] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 00:41:14 localhost kernel: [14620.492264] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 02:22:16 localhost kernel: [20682.452430] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 10:07:01 localhost kernel: [48567.471949] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Nov 10 10:24:23 localhost kernel: [ 2.814167] kmemleak: Kernel memory leak detector initialized Nov 10 10:24:23 localhost kernel: [ 2.814169] kmemleak: Automatic memory scanning thread started 查看/sys/kernel/debug/kmemleak日志 [root@wsip-70-182-148-86 ~]#cat /sys/kernel/debug/kmemleak | wc -l 4706 [root@wsip-70-182-148-86 ~]#cat /sys/kernel/debug/kmemleak unreferenced object 0xffff8000e1dce080 (size 128): comm "swapper/0", pid 1, jiffies 4294892835 (age 684.748s) hex dump (first 32 bytes): 00 70 ec e2 00 80 ff ff 03 00 00 00 05 00 00 00 .p.............. 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000f2295178>] kmem_cache_alloc_trace+0x138/0x230 [<00000000fe5aa91d>] selinux_sb_alloc_security+0x30/0x98 [<00000000345b4d79>] security_sb_alloc+0x30/0x50 [<00000000ab4bc082>] sget_userns+0x16c/0x4c8 [<00000000832e6498>] sget+0x88/0xb8 [<00000000bd79c97f>] mount_single+0x48/0xd8 [<000000005caf29b9>] sel_mount+0x3c/0x50 [<00000000b6f4d911>] mount_fs+0x50/0x280 [<000000003eff9f49>] vfs_kern_mount.part.10+0x54/0x188 [<000000008cdafa20>] kern_mount_data+0x38/0x58 [<000000005e17d84c>] init_sel_fs+0xa4/0x138 [<00000000e7d478c1>] do_one_initcall+0x54/0x220 [<0000000019ba2fa5>] kernel_init_freeable+0x2b0/0x3a0 [<000000008d87871a>] kernel_init+0x18/0x118 [<00000000aba7c0d0>] ret_from_fork+0x10/0x18 [<00000000213be9f5>] 0xffffffffffffffff
评论 (
2
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
修复中
已确认
已完成
已验收
已取消
负责人
未设置
标签
sig/Kernel
issue_wontfix
未设置
项目
未立项任务
未立项任务
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (
-
)
标签 (
-
)
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
预计工期
(小时)
参与者(3)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
评论
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册