Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v3 2/2] package/btrfs-progs: bump to version 7.1
Date: Tue, 18 Aug 2026 23:48:00 +0200	[thread overview]
Message-ID: <aoTSw0AjOev0Ae2M@windsurf> (raw)
In-Reply-To: <20260802194421.1914703-2-fiona.klute@gmx.de>

Hello,

On Sun, Aug 02, 2026 at 09:44:21PM +0200, Fiona Klute via buildroot wrote:
> Upstream changelog:
> https://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git/tree/CHANGES?h=v7.1
> 
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
> ---
> Changes v2 -> v3:
> * update to btrfs-progs 7.1 instead of 7.0

Thanks, applied.

Please note that generating a btrfs filesystem fails for me, but it
already failed before your bump. I think the issue was already
discussed with Julien and is SELinux related:

ERROR: zoned: unable to stat /home/thomas/projets/buildroot/output/images/rootfs.btrfs
NOTE: several default settings have changed in version 5.15, please make sure
      this does not affect your deployments:
      - DUP for metadata (-m dup)
      - enabled no-holes (-O no-holes)
      - enabled free-space-tree (-R free-space-tree)

Rootdir from:       /home/thomas/projets/buildroot/output/build/buildroot-fs/btrfs/target
ERROR: getting a xattr value failed for /home/thomas/projets/buildroot/output/build/buildroot-fs/btrfs/target attr security.selinux: No data available
ERROR: failed to add xattr item for the top level inode: Operation not permitted
ERROR: failed to copy rootdir inode: Operation not permitted
ERROR: unable to traverse directory /home/thomas/projets/buildroot/output/build/buildroot-fs/btrfs/target: 1
/home/thomas/projets/buildroot/output/build/buildroot-fs/btrfs/fakeroot: line 11: 539047 Segmentation fault         (core dumped) /home/thomas/projets/buildroot/output/host/bin/mkfs.btrfs -f -r '/home/thomas/projets/buildroot/output/build/buildroot-fs/btrfs/target' -L '' --byte-count '100m' --nodesize '16384' --sectorsize '4096' /home/thomas/projets/buildroot/output/images/rootfs.btrfs
make: *** [fs/btrfs/btrfs.mk:55: /home/thomas/projets/buildroot/output/images/rootfs.btrfs] Error 139

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-18 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 19:44 [Buildroot] [PATCH v3 1/2] package/fakeroot: bump to version 2.1.4 Fiona Klute via buildroot
2026-08-02 19:44 ` [Buildroot] [PATCH v3 2/2] package/btrfs-progs: bump to version 7.1 Fiona Klute via buildroot
2026-08-18 21:48   ` Thomas Petazzoni via buildroot [this message]
2026-08-18 23:35     ` Fiona Klute via buildroot
2026-08-19 11:43       ` Thomas Petazzoni via buildroot
2026-08-18 21:46 ` [Buildroot] [PATCH v3 1/2] package/fakeroot: bump to version 2.1.4 Thomas Petazzoni via buildroot

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=aoTSw0AjOev0Ae2M@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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