From: "Gero Schwäricke via buildroot" <buildroot@buildroot.org>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH 1/2] support/scripts/genimage.sh: support creating a bmap image
Date: Wed, 24 Apr 2024 09:50:55 +0200 [thread overview]
Message-ID: <20240424075055.GA1370614@theia> (raw)
In-Reply-To: <57d8570c-8825-41a3-8763-64d9589af492@theobroma-systems.com>
Hi Quentin,
On Tue, Apr 23, 2024 at 02:55:57PM +0200, Quentin Schulz via buildroot wrote:
> Hi Gero,
>
> On 4/23/24 13:33, Gero Schwäricke via buildroot wrote:
> > Hi Dario,
> >
> > I tried your patch, but it didn't work for me. bmaptool failed with an
> > error. The issue was that my home directory is encrypted using ecryptfs.
> > This does not implement all ioctl options that are needed for bmaptool
> > to read the block allocation of the image file. There also seem to be
> > issues with ZFS, so I would recommend to not enable this by default for
> > defconfigs.
> >
>
> Is this something you could report to the upstream project?
>
> https://github.com/yoctoproject/bmaptool/
I reported my finding upstream in
https://github.com/yoctoproject/bmaptool/issues/22
though I don't expect a fix. Iiuc the issue is that ecryptfs does not
support the ioctl FIEMAP, which bmaptool needs to find the holes in
a file. So it would require implementing this for the ecryptfs kernel
module (if even possible) and then it'll take a while for that to hit
the mayor Linux distributions. But maybe a new command to bmaptool
could help in the midterm, like `bmaptool verify --check-fs`, so this
case could be detected and handled gracefully in scripts.
>
> The ZFS issue seems to be documented, c.f.
> https://github.com/yoctoproject/bmaptool/?tab=readme-ov-file#known-issues
Yes, and it's fixable for ZFS. But I expect mailtraffic might increase
if bmaptool would be used by default in buildroot. That's why I would
recommend not to apply this to buildroot provided defconfigs
(PATCH 2/2). But I'm much in favor of supporting bmaptool in general
(PATCH 1/2).
Best,
Gero
>
> Cheers,
> Quentin
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
–––
grandcentrix GmbH | A Vodafone Company · Holzmarkt 1 · 50676
*Cologne* | Phoenixseestrasse 18 · 44263 *Dortmund* · Germany
| in
<https://www.linkedin.com/company/grandcentrix> | phone: +49-221-677-860-0
| email: hello@grandcentrix.net <mailto:hello@grandcentrix.net>
grandcentrix cares about privacy
<https://grandcentrix.net/de/pages/privacymail/>
Amtsgericht Köln | HRB
70119 | Geschäftsführer: M. Krömer, R. Hänel | USt.-IdNr.: DE266333969
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-24 7:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 9:53 [Buildroot] [RFC PATCH 0/2] Add support to genimage.sh for creating a bmap image Dario Binacchi
2024-04-21 9:53 ` [Buildroot] [RFC PATCH 1/2] support/scripts/genimage.sh: support " Dario Binacchi
2024-04-23 11:33 ` Gero Schwäricke via buildroot
2024-04-23 12:55 ` Quentin Schulz via buildroot
2024-04-24 7:50 ` Gero Schwäricke via buildroot [this message]
2024-04-24 8:06 ` Gero Schwäricke via buildroot
2024-05-10 19:54 ` Thomas Petazzoni via buildroot
2024-05-10 20:17 ` Michael Nazzareno Trimarchi
2024-05-21 5:25 ` Yann E. MORIN
2024-05-21 9:28 ` Michael Nazzareno Trimarchi
2024-05-21 17:44 ` Yann E. MORIN
2024-05-22 15:19 ` Gero Schwäricke via buildroot
2024-05-31 9:47 ` Thomas Petazzoni via buildroot
2024-05-31 9:44 ` Thomas Petazzoni via buildroot
2024-05-20 8:05 ` Dario Binacchi
2024-05-20 9:23 ` Thomas Petazzoni via buildroot
2024-05-21 15:06 ` Dario Binacchi
2024-05-21 20:36 ` Yann E. MORIN
2024-05-22 15:59 ` Gero Schwäricke via buildroot
2024-07-15 14:05 ` Thomas Petazzoni via buildroot
2024-07-15 14:23 ` Arnout Vandecappelle via buildroot
2024-07-15 14:27 ` Thomas Petazzoni via buildroot
2024-07-16 6:16 ` Dario Binacchi
2024-08-27 18:55 ` Peter Korsgaard
2024-08-28 13:42 ` Thomas Petazzoni via buildroot
2024-08-28 13:58 ` Peter Korsgaard
2024-08-29 21:44 ` Thomas Petazzoni via buildroot
2024-08-30 7:14 ` Peter Korsgaard
2024-08-30 15:29 ` Thomas Petazzoni via buildroot
2024-08-30 15:32 ` Michael Nazzareno Trimarchi
2024-08-31 13:28 ` Peter Korsgaard
2024-08-31 13:20 ` Peter Korsgaard
2024-04-21 9:53 ` [Buildroot] [RFC PATCH 2/2] configs/ti_am62x_sk_defconfig: create the " Dario Binacchi
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=20240424075055.GA1370614@theia \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=gero.schwaericke@grandcentrix.net \
--cc=quentin.schulz@theobroma-systems.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