Hello list.
I'm struggling with a problem involving some orphan descriptors I
found in a crash dump.
I'd like to know who created or inherited (as in fork) them. I mustn't
talk ill of the dead, but they are my prime suspects because of this
(doesn't shows with ps):
[49886.362859] umount.nfs[8425]: segfault at 19... bla bla
Given what I read[1,2], there doesn't seem to be a direct way to get
the struct file (which contains a PID) out of the inode.
--crash dump--
|
v
struct inode <-- this is what I have!
^
|
struct file <--> next/prev file, PID I want (probably)
^
|
struct files_struct
^
|
struct task_struct
I don't know if it's possible to script an iteration with crash over
all tasks in search of a particular inode.
DENTRY INODE TYPE PATH
ffff880936419900 ffff8808d17c5518 REG foo.txt
Any ideas on how to know who created the file descriptors?
Cheers
Ismael
[1] http://www.tldp.org/LDP/tlk/ds/ds.html
[2] http://www.tldp.org/LDP/tlk/kernel/processes.html
--
Do not let me induce you to satisfy my curiosity, from an expectation,
that I shall gratify yours. What I may judge proper to conceal, does
not concern myself alone.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
