mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Stephen Von Takach <steve@place.technology>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com, Viv Briffa <viv@place.technology>
Subject: Re: [musl] unlink on NFS volume fails silently
Date: Thu, 10 Jul 2025 09:01:57 +1000	[thread overview]
Message-ID: <CAASffouYkGz5q9oCJNigPnNURbqNwevAD5TzewKmrV+c9RQQDg@mail.gmail.com> (raw)
In-Reply-To: <20250709184153.GP1827@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

We're using docker containers running on the same kernel using the same
mount setup.
Works on debian, does not work on alpine.

The difference is at the libc interface.


Stephen von Takach Dukai

Engineering Lead

PlaceOS

Australia, Hong Kong, London, New York

p: +61 408 419 954

e: steve@place.technology


On Thu, 10 Jul 2025 at 04:41, Rich Felker <dalias@libc.org> wrote:

> On Wed, Jul 09, 2025 at 01:59:18PM +1000, Stephen Von Takach wrote:
> > Yes we traced this.
> > The libc unlink function on musl returned 0 for a filename on an NFS
> mount
> > that wasn't deleted.
> > https://www.gnu.org/software/libc/manual/html_node/Deleting-Files.html
> >
> > The same call to unlink on glibc returned 0 and actually removed the
> file.
>
> They are not doing anything different. If you're getting a different
> result, it's something else different about the systems, possibly as
> random as timing differences between the program using musl and the
> one using glibc. But I would also check for different kernel versions
> or configurations, mount setups, etc.
>
> > The issue occurs when there is a high volume of files being removed
>
> Sounds like a timing dependent bug in the NFS implementation.
>
> Rich
>

[-- Attachment #2: Type: text/html, Size: 4695 bytes --]

  reply	other threads:[~2025-07-09 23:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06  6:25 [musl] unlink on NFS volume fails silently Stephen Von Takach
2025-07-07 18:26 ` Markus Wichmann
2025-07-08  1:08 ` Rich Felker
2025-07-09  3:59   ` [musl] " Stephen Von Takach
2025-07-09 18:41     ` Rich Felker
2025-07-09 23:01       ` Stephen Von Takach [this message]
2025-07-10  0:03         ` Rich Felker
2025-07-10  4:58           ` Stephen Von Takach
2025-07-10 15:44             ` Rich Felker
2025-07-10 17:01               ` Nathan McSween
2025-07-10 17:11                 ` Rich Felker
2025-07-10 21:25               ` Stephen Von Takach

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=CAASffouYkGz5q9oCJNigPnNURbqNwevAD5TzewKmrV+c9RQQDg@mail.gmail.com \
    --to=steve@place.technology \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=viv@place.technology \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).