容器启动挂载/var/lib/lxc/lxcfs/sys/devices/system/cpu，进行htop操作，产生了coredump

**【标题描述】能够简要描述问题：说明什么场景下，做了什么操作，出现什么问题（尽量使用正向表达方式）**
**一、缺陷信息**
容器启动挂载参数中含有-v /var/lib/lxc/lxcfs/sys/devices/system/cpu:/sys/devices/system/cpu:rw时，进行htop操作，产生了coredump（Segmentation fault）
**内核信息：**
5.10.0-136.12.0.86.oe2203sp1.x86_64
**缺陷归属组件：**
htop
**缺陷归属的版本：**
htop-3.1.2-1.oe2203.x86_64
**缺陷简述：**
容器启动挂载参数中含有-v /var/lib/lxc/lxcfs/sys/devices/system/cpu:/sys/devices/system/cpu:rw时，进行htop操作，产生了coredump（Segmentation fault）
**【环境信息】**
硬件信息
- 裸机场景请提供问题的硬件信息
- 虚拟机场景请提供虚拟机的XML文件或配置信息
软件信息
- OS版本及分支信息
[root@localhost usr]# cat /etc/os-release 
NAME="openEuler"
VERSION="22.03 (LTS-SP1)"
ID="openEuler"
VERSION_ID="22.03"
PRETTY_NAME="openEuler 22.03 (LTS-SP1)"
ANSI_COLOR="0;31"
- 内核信息
5.10.0-136.12.0.86.oe2203sp1.x86_64
- 发现问题的组件版本信息
网络信息
- 如果有特殊组网，请提供网络拓扑信息
**【问题复现步骤】**，请描述具体的操作步骤
1、安装并启动lxcfs和docker服务，下载容器镜像
2、启动容器docker run -itd -v /var/lib/lxc/lxcfs/sys/devices/system/cpu:/sys/devices/system/cpu:rw openeuler-22.03-lts-sp1:latest /bin/bash
3、容器中安装htop包，执行htop命令
**【实际结果】**，请描述出问题的结果和影响
报错产生core文件
FATAL PROGRAM ERROR DETECTED
============================
Please check at https://htop.dev/issues whether this issue has already been reported.
If no similar issue has been reported before, please create a new issue with the following information:
  - Your htop version: '3.1.2'
  - Your OS and kernel version (uname -a)
  - Your distribution and release (lsb_release -a)
  - Likely steps to reproduce (How did it happen?)
  - Backtrace of the issue (see below)

Error information:
------------------
A signal 11 (Segmentation fault) was received.

Setting information:
--------------------
htop_version=3.1.2;config_reader_min_version=2;fields=0 48 17 18 38 39 40 2 46 47 49 1;sort_key=46;sort_direction=-1;tree_sort_key=0;tree_sort_direction=1;hide_kernel_threads=1;hide_userland_threads=0;shadow_other_users=0;show_thread_names=0;show_program_path=1;highlight_base_name=0;highlight_deleted_exe=1;highlight_megabytes=1;highlight_threads=1;highlight_changes=0;highlight_changes_delay_secs=5;find_comm_in_cmdline=1;strip_exe_from_cmdline=1;show_merged_command=0;tree_view=0;tree_view_always_by_pid=0;all_branches_collapsed=0;header_margin=1;detailed_cpu_time=0;cpu_count_from_one=0;show_cpu_usage=1;show_cpu_frequency=0;update_process_names=0;account_guest_in_cpu_meter=0;color_scheme=0;enable_mouse=1;delay=15;hide_function_bar=0;header_layout=two_50_50;column_meters_0=AllCPUs Memory Swap;column_meter_modes_0=1 1 1;column_meters_1=Tasks LoadAverage Uptime;column_meter_modes_1=2 2 2;

Backtrace information:
----------------------
htop(+0x14cbb)[0x562973fc3cbb]
htop(CRT_handleSIGSEGV+0xdb)[0x562973fc3ecb]
/lib64/libc.so.6(+0x40ed0)[0x7f1a139f6ed0]
htop(+0x2a8c7)[0x562973fd98c7]
htop(ProcessList_goThroughEntries+0x9a6)[0x562973fdc606]
htop(ProcessList_scan+0xab)[0x562973fd0d0b]
htop(CommandLine_run+0x35b)[0x562973fc25db]
/lib64/libc.so.6(+0x2d210)[0x7f1a139e3210]
/lib64/libc.so.6(__libc_start_main+0x7c)[0x7f1a139e32bc]
htop(_start+0x25)[0x562973fbea95]

To make the above information more practical to work with, please also provide a disassembly of your htop binary. This can usually be done by running the following command:

objdump -d -S -w `which htop` > ~/htop.objdump

Please include the generated file in your report.
Running this program with debug symbols or inside a debugger may provide further insights.

Thank you for helping to improve htop!

Segmentation fault (core dumped)

src-openEuler/htop
Closed

Content Risk Flag

Comments (5)

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

Content Risk Flag