public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Miell <nmiell@comcast.net>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: [PATCH 0/3] *at syscalls: Intro
Date: Thu, 15 Dec 2005 17:13:52 -0800	[thread overview]
Message-ID: <1134695632.2785.12.camel@entropy> (raw)
In-Reply-To: <200512152249.jBFMnXAA016747@devserv.devel.redhat.com>

On Thu, 2005-12-15 at 17:49 -0500, Ulrich Drepper wrote:
> Here is a series of patches which introduce in total 11 new system calls
> which take a file descriptor/filename pair instead of a single file name.
> These functions, openat etc, have been discussed on numerous occasions.
> They are needed to implement race-free filesystem traversal, they are
> necessary to implement a virtual per-thread current working directory
> (think multi-threaded backup software), etc.
> 

Actually, that last part is false (or maybe just misleading). You can
create threads without CLONE_FS to get a per-thread cwd/chroot/umask, no
"virtual" required.

Don't take this as an objection to implementation of the *at() syscalls
in Linux, though; rather, look at is as a request for the addition of
int pthread_attr_setfssharing_np(pthread_attr_t *attr, int share) and
int pthread_attr_getfssharing_np(pthread_attr_t *attr) to glibc.

-- 
Nicholas Miell <nmiell@comcast.net>


  parent reply	other threads:[~2005-12-16  1:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 22:49 [PATCH 0/3] *at syscalls: Intro Ulrich Drepper
2005-12-16  0:32 ` Jeff Garzik
2005-12-16  1:29   ` Ulrich Drepper
2005-12-16  1:39     ` Jeff Garzik
2005-12-16 11:32   ` Jim Meyering
2005-12-16 16:24     ` Ulrich Drepper
2005-12-16 16:36       ` Jakub Jelinek
2005-12-16 19:59       ` Jim Meyering
2005-12-16  1:13 ` Nicholas Miell [this message]
2005-12-16 17:51   ` Linus Torvalds

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=1134695632.2785.12.camel@entropy \
    --to=nmiell@comcast.net \
    --cc=akpm@osdl.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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