From: ebiederm@xmission.com (Eric W. Biederman)
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
linux-api@vger.kernel.org,
"Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REVIEW][PATCH 0/4] /proc/thread-self
Date: Fri, 01 Aug 2014 00:01:13 -0700 [thread overview]
Message-ID: <8738dgae2u.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <53DB3790.7020600@infradead.org> (Randy Dunlap's message of "Thu, 31 Jul 2014 23:45:36 -0700")
Randy Dunlap <rdunlap@infradead.org> writes:
> On 07/31/14 17:30, Eric W. Biederman wrote:
>>
>> This patchset implements /proc/thread-self a magic symlink that
>> solves a couple of problems.
>>
>> - It makes it easy to get to a specific threads directory in /proc
>> with gettid() not being exported in glibc this is currently a pain.
>>
>> - It allows fixing the problem present in /proc/mounts and /proc/net
>> that when the thread group leader exits but the entire thread group
>> remains /proc/self/net and /proc/self/mounts and thus /proc/mounts and
>> /proc/net become empty.
>>
>> - As mount and network namespaces are per thread it allows /proc/net and
>> /proc/mounts to reflect this.
>
> Hi Eric,
>
> Any changes/additions to Documentation/ ?
Not at this time. I can imagine that there is proc manpage that might
need a line or two of Documentation.
I am not familiar with anything in Documentation that descripes any of
this and would benefit from an update. From an overview perspective I
can see documenting this so people know thread-self exists. From an
actual usage perspective:
$ ls -l /proc/thread-self
lrwxrwxrwx 1 root root 0 Aug 1 00:00 /proc/thread-self -> 484/task/484
seems like pretty comprehensive documentation to me.
Eric
next prev parent reply other threads:[~2014-08-01 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 0:30 [REVIEW][PATCH 0/4] /proc/thread-self Eric W. Biederman
2014-08-01 0:33 ` [REVIEW][PATCH 1/4] proc: Have net show up under /proc/<tgid>/task/<tid> Eric W. Biederman
2014-08-01 0:34 ` [REVIEW][PATCH 2/4] proc: Implement /proc/thread-self to point at the directory of the current thread Eric W. Biederman
2014-08-06 14:35 ` Serge E. Hallyn
2014-08-06 18:22 ` Eric W. Biederman
2014-08-06 18:32 ` Serge Hallyn
2014-08-01 0:34 ` [REVIEW][PATCH 3/4] proc: Point /proc/net at /proc/thread-self/net instead of /proc/self/net Eric W. Biederman
2014-08-01 0:35 ` [REVIEW][PATCH 4/4] proc: Point /proc/mounts at /proc/thread-self/mounts instead of /proc/self/mounts Eric W. Biederman
2014-08-01 2:39 ` [REVIEW][PATCH 0/4] /proc/thread-self Davidlohr Bueso
2014-08-01 6:16 ` Eric W. Biederman
2014-08-04 13:12 ` Karel Zak
2014-08-01 6:45 ` Randy Dunlap
2014-08-01 7:01 ` Eric W. Biederman [this message]
2014-08-01 7:14 ` Bert Wesarg
2014-08-01 7:45 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738dgae2u.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox