public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>,
	Paul Eggert <eggert@cs.ucla.edu>, Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org, Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: [PATCH] Add renameat2 function [BZ #17662]
Date: Wed, 04 Jul 2018 20:26:00 -0000	[thread overview]
Message-ID: <277401d5-b21d-61aa-ee9d-4417614a9656@redhat.com> (raw)
In-Reply-To: <59d43024-6c94-9444-929d-03868b092b57@redhat.com>

On 07/04/2018 10:13 PM, Carlos O'Donell wrote:
> This is a good suggestion, and I think Florian should work on something
> going into the manual to document the behaviour.

We do not have any documentation for the *at functions at present.  I 
find it difficult to document renameat2 without reference to openat and 
a generic description of the AT_* flags.  I feel this is something we 
should tackle after the release.

Once the patch is in, I will propose something for the existing manual 
page, documenting the EINVAL behavior of the glibc wrapper and the 
existence of the gnulib implementation.

> You position Gnulib's implementation as having no drawbacks, but this
> is not true. The API has a race, and it is something which along with
> other similar racy APIs has caused difficult to solve problems a the
> distribution level.

And as Joseph pointed out, there is a different emulation strategy with 
a different failure mode (use link and potentially leave behind a 
hard-linked file under both names).

Thanks,
Florian

  reply	other threads:[~2018-07-04 20:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 12:15 Florian Weimer
2018-06-30 20:22 ` Joseph Myers
2018-06-30 21:11   ` Florian Weimer
2018-06-30 22:26     ` Joseph Myers
2018-07-01 21:49 ` Yury Norov
2018-07-02  6:48   ` Florian Weimer
2018-07-02  8:46     ` Yury Norov
2018-07-02  9:32       ` Florian Weimer
2018-07-02  8:59   ` Andreas Schwab
2018-07-02 15:11   ` Joseph Myers
2018-07-02 17:38 ` Paul Eggert
2018-07-02 19:46   ` Joseph Myers
2018-07-02 19:58     ` Paul Eggert
2018-07-03  6:40   ` Florian Weimer
2018-07-03 19:06     ` Paul Eggert
2018-07-04  9:04       ` Andreas Schwab
2018-07-04 10:39         ` Florian Weimer
2018-07-04 16:31         ` Carlos O'Donell
2018-07-04 19:36           ` Paul Eggert
2018-07-04 20:13             ` Carlos O'Donell
2018-07-04 20:26               ` Florian Weimer [this message]
2018-07-04 20:46                 ` Paul Eggert
2018-07-05 13:19                 ` Carlos O'Donell
2018-07-04 20:47               ` Paul Eggert
2018-07-04 19:21 ` Carlos O'Donell
2018-07-04 19:53   ` Paul Eggert
2018-07-04 20:28     ` Florian Weimer
2018-07-04 20:36       ` Paul Eggert
2018-07-05 14:01   ` Florian Weimer
2018-07-05 14:25     ` Paul Eggert
2018-07-05 15:26       ` Florian Weimer
2018-07-05 16:53         ` Paul Eggert
2018-07-05 16:57     ` Carlos O'Donell

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=277401d5-b21d-61aa-ee9d-4417614a9656@redhat.com \
    --to=fweimer@redhat.com \
    --cc=bug-gnulib@gnu.org \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@suse.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).