From: Andi Kleen <andi@firstfloor.org>
To: linux-fsdevel@vger.kernel.org
Cc: containers@lists.osdl.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [REVIEW][PATCH 0/4] /proc/thread-self
Date: Mon, 04 Aug 2014 07:47:04 -0700 [thread overview]
Message-ID: <87lhr4pb13.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: 87oaw5caq1.fsf@x220.int.ebiederm.org
ebiederm@xmission.com (Eric W. Biederman)
writes:
> 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.
syscall(__NR_gettid);
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2014-08-04 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 0:30 [REVIEW][PATCH 0/4] /proc/thread-self Eric W. Biederman
[not found] ` <87oaw5caq1.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
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
[not found] ` <87bns5cakh.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2014-08-06 14:35 ` Serge E. Hallyn
[not found] ` <20140806143500.GA23127-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2014-08-06 18:22 ` Eric W. Biederman
[not found] ` <871tsttr4u.fsf@x220.int.ebiederm.org>
[not found] ` <871tsttr4u.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
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:45 ` Randy Dunlap
2014-08-01 7:14 ` Bert Wesarg
[not found] ` <1406860795.3036.3.camel@buesod1.americas.hpqcorp.net>
[not found] ` <1406860795.3036.3.camel-5JQ4ckphU/8SZAcGdq5asR6epYMZPwEe5NbjCUgZEJk@public.gmane.org>
2014-08-01 6:16 ` Eric W. Biederman
2014-08-04 13:12 ` Karel Zak
[not found] ` <53DB3790.7020600@infradead.org>
[not found] ` <53DB3790.7020600-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-08-01 7:01 ` Eric W. Biederman
[not found] ` <CAKPyHN1k80fc0hkg7agMkCMDsb623=Zf-TrpyMiMLvtYEjz3_Q@mail.gmail.com>
[not found] ` <CAKPyHN1k80fc0hkg7agMkCMDsb623=Zf-TrpyMiMLvtYEjz3_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-01 7:45 ` Eric W. Biederman
2014-08-04 14:47 ` Andi Kleen [this message]
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=87lhr4pb13.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=containers@lists.osdl.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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