linux-kernel - Inode entry of a process in /proc/pid changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 6 Feb 2014 20:27:27 +0530
From:	navin p <navinp1281@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Inode entry of a process in /proc/pid changes

Hi,
        I am running RHEL 6.4 on  2.6 linux x64 on one of our customer server.
When there is a stress or the server is highly loaded by one of the backup
agents the inode number (got from ls -i /proc/<pid> or ls -i
/proc/<pid>/task/<tid> ) changes. If you don't put any stress/load on the
system , the inode number remains intact.
 I have a few questions for troubleshooting this problem .

1) Can /proc be mounted so that the inode numbers of a process and its
tasks (threads) don't changed unless it is a new process ?

2) How is the proc file system created /freed  and subentries under it?

3)Why do the inode numbers change. I understand for a newly created process
it could have a new inode number but for a long running process like init
why does it change ever ?

Can someone point out source links to the latest kernel version so that i
can understand it better ?

Thank you,
Navin Parakkal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/