[lkml]   [2014]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectexecve and /proc/PID/environ
Hi - this is my first post here so I hope I'm duly abiding by the
etiquette outlined in [1]. Indeed I am not subscribed to the list and
so would be very grateful to be copied on any replies, per ADB's
comment in [2]

I am trying to build a fuse-based file system that implements a
version of variant symlinks [3]

Ignoring the expense of such a file system (for now at least), I've
hit upon an issue that I think relates to [4]

My fuse-based file system works by examining the environment of the
calling process in order to resolve the 'symlink'. If however that
process is performing an execve [5] with a filename argument that
corresponds to a file within my file system, I essentially hit
deadlock because I can't perform an open [6] on the /proc/PID/environ
of the calling process.

Perhaps someone can confirm the behaviour I am seeing is as expected?

In this instance (where an execve is in progress), is there any way to
get the environ of the calling process?

For reference:

$ uname -s -r -v -m -p -i -o
Linux 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

Many thanks


 \ /
  Last update: 2014-03-17 22:01    [W:0.033 / U:2.800 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site