Skip to contentSkip to conversation

Dumpable tasks and ownership of /proc/*/fd

DISCUSSION Bodo Eggert 1 participant 1 message Apr 11, 2006 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 9 lines · Eric W. Biederman

Speaking of things why does the *at() emulation need to touch /proc/self/fd/*? I may be completely dense but if the practical justification for allowing access to /proc/self/fd/ is that we already have access then we shouldn't need /proc/self/fd.

I suspect this a matter of convenience where you are prepending /proc/self/fd/xxx/ to the path before you open it instead of calling fchdir openat() and the doing fchdir back. Have I properly guessed how the *at() emulation works?

Think about threads or siglongjmp(sp?).

Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.