All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lander0606" <landervanloock@gmail.com>
To: "Gyorgy Sarvari" <skandigraun@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Btrfs root filesystem permission issue
Date: Sat, 01 Mar 2025 07:56:34 -0800	[thread overview]
Message-ID: <4647.1740844594426429510@lists.yoctoproject.org> (raw)
In-Reply-To: <1adcf6c5-d4be-4701-948c-3a6425f3da07@gmail.com>

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

Thanks for your response!

I did have a look at the pseudo and btrfs-progs repository and noticed that the pseudo repository contains the following code in ./ports/unix/guts/ for the nftw() system call:

rc = real_nftw(path, fn, nopenfd, flag);

So, it seems that the wrapper for the nftw() system call just forwards it to the underlying system (the host, right?). Is that the reason why the btrfs filesystem creation does work, but files are owned by the build host user?
I'm guessing there need to be some code around it to support the "fake root environment" that pseudo is trying to achieve?

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

  reply	other threads:[~2025-03-01 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 18:57 Btrfs root filesystem permission issue Lander0606
2025-03-01 14:35 ` [yocto] " Gyorgy Sarvari
2025-03-01 15:56   ` Lander0606 [this message]
2025-03-01 17:05     ` Gyorgy Sarvari
2025-03-01 18:32       ` Lander0606
2025-03-03 12:08         ` Gyorgy Sarvari
2025-03-03 21:52           ` Lander0606
2025-03-03 21:57             ` Gyorgy Sarvari
2025-03-03 22:05               ` Lander0606
2025-03-04  0:14                 ` Lander0606
2025-04-24 20:18   ` Ferry Toth
2025-04-25  6:21     ` Gyorgy Sarvari

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=4647.1740844594426429510@lists.yoctoproject.org \
    --to=landervanloock@gmail.com \
    --cc=skandigraun@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.