linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	jeremy@goop.org, jengelh@computergmbh.de, viro@ftp.linux.org.uk,
	nmiell@comcast.net, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: *at syscalls for xattrs?
Date: Mon, 16 Jul 2007 13:40:23 -0700	[thread overview]
Message-ID: <469BD7B7.30009@zytor.com> (raw)
In-Reply-To: <469BCF0C.6070109@garzik.org>

Jeff Garzik wrote:
>>
>> Well, as Jeremy pointed out, in the absence of threads you can do the
>> same thing with fchdir(), however, that's much more of a hack.
> 
> My posixutils project (coreutils replacement) used fchdir(2), but that
> still doesn't get you 100% race-free.  It gets you close, yes.
> 

I guess you're horked in the case where a single system call (e.g.
rename()) needs more than one pathname.  Yet another reason why a single
cwd isn't enough.

	-hpa

  reply	other threads:[~2007-07-16 20:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 19:46 *at syscalls for xattrs? Jan Engelhardt
2007-07-15 20:53 ` Al Viro
2007-07-15 21:13   ` Nicholas Miell
2007-07-15 22:23     ` Al Viro
2007-07-15 23:09       ` H. Peter Anvin
2007-07-16  7:56       ` Jan Engelhardt
2007-07-16  8:04         ` Al Viro
2007-07-16  8:30         ` Jeremy Fitzhardinge
2007-07-16  9:05           ` Miklos Szeredi
2007-07-16  9:33             ` H. Peter Anvin
2007-07-16  9:47               ` Jeff Garzik
2007-07-16 17:57                 ` H. Peter Anvin
2007-07-16 20:03                   ` Jeff Garzik
2007-07-16 20:40                     ` H. Peter Anvin [this message]
2007-07-16  9:12           ` Andreas Schwab

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=469BD7B7.30009@zytor.com \
    --to=hpa@zytor.com \
    --cc=jeff@garzik.org \
    --cc=jengelh@computergmbh.de \
    --cc=jeremy@goop.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=nmiell@comcast.net \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).