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

On Thu, Jul 10, 2025 at 09:01:57AM +1000, Stephen Von Takach wrote:
> 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.

Unless I'm missing something, musl and glibc are doing exactly the
same thing here. There is no userspace code for unlink; it's just a
syscall. You can compare the glibc code at:

https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/unlink.c;hb=glibc-2.41

with the musl code at:

https://git.musl-libc.org/cgit/musl/tree/src/unistd/unlink.c?id=v1.2.5

If you're seeing different behavior, something else is the cause. It's
almost surely what I said, a timing-dependent NFS bug.

Rich


  reply	other threads:[~2025-07-10  0:03 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       ` [musl] " Stephen Von Takach
2025-07-10  0:03         ` Rich Felker [this message]
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=20250710000328.GT1827@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=steve@place.technology \
    --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).