unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Avoid concurrency problem in ldconfig (bug 23973)
Date: Thu, 18 Apr 2019 16:47:34 +0200	[thread overview]
Message-ID: <87zhonv08p.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <mvmv9zbpiyl.fsf@suse.de> (Andreas Schwab's message of "Thu, 18 Apr 2019 14:59:46 +0200")

* Andreas Schwab:

> On Apr 18 2019, Florian Weimer <fweimer@redhat.com> wrote:
>
>> * Andreas Schwab:
>>
>>> Use a unique name for the temporary file when updating the ld.so cache, so
>>> that two concurrent runs of ldconfig don't write to the same file.
>>>
>>> 	* elf/cache.c (save_cache): Use unique temporary name.
>>> 	(save_aux_cache): Likewise.
>>
>> The downside of this change is that if ldconfig is interrupted, the
>> temporary file never goes away.
>>
>> Ideally, we would use O_TMPFILE if supported by the (file) system, but
>> that can get quite involved.
>
> That shortens the window, but won't close it, since we need a name to
> pass to rename in any case.

The difference is that with a fixed name, the next ldconfig run will use
the same name and rename, cleaning up.  With a random, unique name, that
automatic cleanup is gone.

Thanks,
Florian

  reply	other threads:[~2019-04-18 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 16:51 [PATCH] Avoid concurrency problem in ldconfig (bug 23973) Andreas Schwab
2019-04-18 12:01 ` Florian Weimer
2019-04-18 12:09   ` Christian Brauner
2019-04-18 12:11     ` Florian Weimer
2019-04-18 12:59   ` Andreas Schwab
2019-04-18 14:47     ` Florian Weimer [this message]
2019-04-18 15:16       ` Andreas Schwab
2019-04-18 15:52         ` Florian Weimer
2019-04-18 16:04           ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2019-01-21 15:30 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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhonv08p.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --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).