[Crash-utility] Re: [PATCH v3] add "files -n" command for an inode
Hi Kazu,
在 2023/12/2 21:21, Shijie Huang 写道:
在 2023/11/9 12:37, HAGIO KAZUHITO(萩尾 一仁) 写道:
> [EXTERNAL EMAIL NOTICE: This email originated from an external
> sender. Please be mindful of safe email handling and proprietary
> information protection practices.]
>
>
> On 2023/11/08 19:00, lijiang wrote:
>
>>> Then "files -p" option also emits the same error?
>>>
>>>
>> Yes. It has the same error:
>> crash> files -p ffff8ea84c130938
>> INODE NRPAGES
>> ffff8ea84c130938 62527
>>
>> PAGE PHYSICAL MAPPING INDEX CNT FLAGS
>> fffff5168860d000 218340000 ffff8ea84c130ab0 0 5 17ffffc0012076
>> referenced,uptodate,lru,active,workingset,private,head
>> files: do_xarray: callback operation failed: entry: 1 item: 0
>>
>> crash> files -n ffff8ea84c130938
>> INODE NRPAGES
>> ffff8ea84c130938 62527
>>
>> files: do_xarray: callback operation failed: entry: 1 item: 0
>>
>> Is that /proc/kcore? What is the kernel version?
>>>
>> Yes, the kernel version is 6.5.0-rc1.
> Thanks, I found a 6.5 environment that could reproduce this.
>
> crash> sys
> KERNEL: /lib/modules/6.5.9/build/vmlinux
I only find v6.5-rc1 ~ v6.5-rc7 in Linus's tree.
What does the 6.5.9 mean?
I tested the stable tree with tag 6.5.9:
crash> sys
KERNEL: /root/linux-stable/vmlinux
DUMPFILE: /proc/kcore
CPUS: 160
DATE: Mon Dec 4 16:07:19 CST 2023
UPTIME: 00:04:24
LOAD AVERAGE: 0.40, 0.16, 0.06
TASKS: 1849
NODENAME: fedora
RELEASE: 6.5.9-stable-crash--00001-g4ecfae36b372
VERSION: #50 SMP PREEMPT Mon Dec 4 15:58:37 CST 2023
MACHINE: aarch64 (unknown Mhz)
MEMORY: 510.8 GB
crash> files
PID: 3210 TASK: ffff07ff8e87ec80 CPU: 45 COMMAND: "crash"
ROOT: / CWD: /root/tool/crash/crash
FD FILE DENTRY INODE TYPE PATH
0 ffff07ff9b4c3c00 ffff07ff99a11980 ffff07ff8beb15f0 CHR /dev/pts/0
1 ffff07ff9b4c3c00 ffff07ff99a11980 ffff07ff8beb15f0 CHR /dev/pts/0
2 ffff07ff9b4c3c00 ffff07ff99a11980 ffff07ff8beb15f0 CHR /dev/pts/0
3 ffff3fff925fba00 ffff07ff80446300 ffff07ff89980c68 CHR /dev/null
4 ffff3fff925fb600 ffff07ff95032f00 ffff07ff90bb23a0 REG /proc/kcore
5 ffff3fff925fbb00 ffff07ffb90d3c80 ffff07ffb90e2a38 REG
/root/linux-stable/vmlinux
6 ffff3fff925fad00 ffff07ff952aab40 ffff07ff8bf58000 FIFO
7 ffff3fff925fae00 ffff07ff952aab40 ffff07ff8bf58000 FIFO
8 ffff3fff925fa100 ffff07ff952ab500 ffff07ff8bf584e0 FIFO
9 ffff3fff925fa900 ffff07ff952ab500 ffff07ff8bf584e0 FIFO
10 ffff3fff925f8500 ffff07ff9990ad80 ffff07ff8bf58750 FIFO
11 ffff3fff925fa000 ffff07ff9990ad80 ffff07ff8bf58750 FIFO
12 ffff3fff925fb800 ffff07ff9990b500 ffff07ff8bf589c0 FIFO
13 ffff3fff925f9b00 ffff07ff9990b500 ffff07ff8bf589c0 FIFO
14 ffff3fff925fbc00 ffff07ffb90d3c80 ffff07ffb90e2a38 REG
/root/linux-stable/vmlinux
15 ffff3fff925fbe00 ffff07ff9990a480 ffff07ff9ac72130 REG /tmp/#66
17 ffff3fff925fb500 ffff07ff9990a840 ffff07ff8bf59110 FIFO
crash> files -n ffff07ffb90e2a38
INODE NRPAGES
ffff07ffb90e2a38 94183
NODE PAGES
0 94183
1 0
time cost:0 s
crash>
I still do not meet the issue.
Thanks
Huang Shijie