linux-kernel - Accessing file-offset info for fds in /proc?

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070220073130.GV5752@timmy.spinoli.org>
Date:	Tue, 20 Feb 2007 02:31:30 -0500
From:	Hank Leininger <hlein@...elogic.com>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Accessing file-offset info for fds in /proc?

Is there anything provided by the kernel that would let you see the
current offset of an existing filehandle?

Sometimes when processing a very large file (grepping a log, bzip2'ing
or gpg'ing a file, or whatever), I'd really like to know how far along
it is, because I'm impatient.  lsof has an -o flag to show offsets for
file descriptors it lists, but it appears that's not supported under
Linux.  It looks like all of the information lsof and fuser print about 
files in use, etc can be gotten from /proc/*/fd/* (and /proc/*/maps, but
I'm not really concerned with mmap'ed files, just positions on fds).
Sometimes I'll resort to strace -s4096'ing the process to see what chunk
of text it's currently reading, and try to guess from that.  Silly.

Has anybody ever developed a patch to implement this?  I realize this
could create a variety of information-leakage problems; the information
probably would need to be restricted, such as by the same rules as
dumpable.  Are there any horribly painful reasons why this couldn't be
done?

Thanks,

-- 

Hank Leininger <hlein@...elogic.com>
F980 A584 5175 1996 DD7E  C47B 1A71 105C CB44 CBF8

Content of type "application/pgp-signature" skipped