public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Ferry Toth <fntoth@gmail.com>,
	linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>
Subject: Re: Errors on newly created file system
Date: Fri, 25 Apr 2025 06:19:17 +0930	[thread overview]
Message-ID: <f32bd559-71c7-4d45-9af4-47a913eca63d@gmx.com> (raw)
In-Reply-To: <d98ffb69-195b-4c07-ac56-8ae1f811af32@gmail.com>



在 2025/4/25 05:41, Ferry Toth 写道:
> Hi
> 
[...]
>>
>>
>> Except with newer mkfs.btrfs (I tested using 6.13) the files are owned 
>> by the unprivileged user.
>>
>>
>> The result is, the image will not boot correctly.
>>
>>
> I found more about this issue here
> 
> https://lore.kernel.org/yocto/ 
> tRtu.1740682678597454399.5171@lists.yoctoproject.org/T/ 
> #m5de0afa17d2c0f640e86ffe67e0d74aea467fd5b
> 
Thanks for the report.

Just want to be sure, with pseudo emulating root environment, how does 
it handle the file uid/gid?

Mkfs.btrfs uses the uid/gid reported from stat() system calls, thus if 
pseudo doesn't change uid/gid reported from stat(), mkfs.btrfs will just 
follow the result.

I guess it's possible for us to implement an idmap-like solution, but 
I'd like to know how pseudo works first.

Thanks,
Qu

  reply	other threads:[~2025-04-24 20:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-20 21:45 Errors on newly created file system Ferry Toth
2025-04-20 22:00 ` Qu Wenruo
2025-04-22 21:32   ` Ferry Toth
2025-04-22 22:00     ` Qu Wenruo
2025-04-23 16:06       ` Ferry Toth
2025-04-23 23:24         ` Qu Wenruo
2025-04-24 11:31           ` Ferry Toth
2025-04-24 20:11             ` Ferry Toth
2025-04-24 20:49               ` Qu Wenruo [this message]
2025-04-24 21:16                 ` Ferry Toth
2025-04-26 21:01                   ` Ferry Toth
2025-04-26 20:42           ` Ferry Toth

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=f32bd559-71c7-4d45-9af4-47a913eca63d@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=fntoth@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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