[OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Pratik Farkase]

The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
including inode and device numbers. On ext4 root filesystems (particularly
qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
or newc 8-hex-digit field widths, causing intermittent assertion failures
in test_format_newc and test_option_c.

Run all tests from a tmpfs working directory where inode numbers always
start small, avoiding the overflow condition.

[YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
 .../libarchive/libarchive/run-ptest              | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
index d6b4c3f934..7f61e1b173 100755
--- a/meta/recipes-extended/libarchive/libarchive/run-ptest
+++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
@@ -1,13 +1,24 @@
 #!/bin/sh
 
+PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
+
 # The fuzz tests run 1000 randomised iterations per archive format and are
 # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
 # regularly time out in the time/memory constrained autobuilder QEMU targets
 # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
 export SKIP_TEST_FUZZ=1
 
+# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
+# including inode and device numbers. On ext4 root filesystems inode numbers
+# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
+# field widths, causing intermittent assertion failures. Run all tests from
+# a tmpfs where inode numbers start fresh and small.
+WORKDIR=$(mktemp -d)
+mount -t tmpfs tmpfs "$WORKDIR"
+cd "$WORKDIR"
+
 for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
-    ./$t
+    "$PTEST_DIR"/$t
     if [ $? -eq 0 ]; then
         echo "PASS: $t"
     else
@@ -15,3 +26,6 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
     fi
 done
 
+cd /
+umount "$WORKDIR"
+rmdir "$WORKDIR"
-- 
2.34.1

Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Paul Barker]

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

On Mon, 2026-07-20 at 14:26 +0200, Pratik Farkase wrote:
> The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
> including inode and device numbers. On ext4 root filesystems (particularly
> qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
> or newc 8-hex-digit field widths, causing intermittent assertion failures
> in test_format_newc and test_option_c.
> 
> Run all tests from a tmpfs working directory where inode numbers always
> start small, avoiding the overflow condition.
> 
> [YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Hi,

Has this issue been reported upstream to libarchive? It would be good to
get the test cases fixed so they can handle whatever inode numbers are
allocated.

> 
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
>  .../libarchive/libarchive/run-ptest              | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
> index d6b4c3f934..7f61e1b173 100755
> --- a/meta/recipes-extended/libarchive/libarchive/run-ptest
> +++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
> @@ -1,13 +1,24 @@
>  #!/bin/sh
>  
> +PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
> +
>  # The fuzz tests run 1000 randomised iterations per archive format and are
>  # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
>  # regularly time out in the time/memory constrained autobuilder QEMU targets
>  # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
>  export SKIP_TEST_FUZZ=1
>  
> +# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
> +# including inode and device numbers. On ext4 root filesystems inode numbers
> +# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
> +# field widths, causing intermittent assertion failures. Run all tests from
> +# a tmpfs where inode numbers start fresh and small.
> +WORKDIR=$(mktemp -d)
> +mount -t tmpfs tmpfs "$WORKDIR"
> +cd "$WORKDIR"
> +
>  for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
> -    ./$t
> +    "$PTEST_DIR"/$t
>      if [ $? -eq 0 ]; then
>          echo "PASS: $t"
>      else
> @@ -15,3 +26,6 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
>      fi
>  done
>  
> +cd /

It's better to use pushd/popd instead of finishing with `cd /`.

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[OE-core][PATCH v2] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Pratik Farkase]

The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
including inode and device numbers. On ext4 root filesystems (particularly
qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
or newc 8-hex-digit field widths, causing intermittent assertion failures
in test_format_newc and test_option_c.

Run all tests from a tmpfs working directory where inode numbers always
start small, avoiding the overflow condition.

[YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
Changes in v2:
- Use cd "$PTEST_DIR" instead of cd / after tests complete
---
 .../libarchive/libarchive/run-ptest              | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
index d6b4c3f934..4af767b29a 100755
--- a/meta/recipes-extended/libarchive/libarchive/run-ptest
+++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
@@ -1,13 +1,24 @@
 #!/bin/sh
 
+PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
+
 # The fuzz tests run 1000 randomised iterations per archive format and are
 # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
 # regularly time out in the time/memory constrained autobuilder QEMU targets
 # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
 export SKIP_TEST_FUZZ=1
 
+# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
+# including inode and device numbers. On ext4 root filesystems inode numbers
+# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
+# field widths, causing intermittent assertion failures. Run all tests from
+# a tmpfs where inode numbers start fresh and small.
+WORKDIR=$(mktemp -d)
+mount -t tmpfs tmpfs "$WORKDIR"
+cd "$WORKDIR"
+
 for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
-    ./$t
+    "$PTEST_DIR"/$t
     if [ $? -eq 0 ]; then
         echo "PASS: $t"
     else
@@ -15,3 +26,6 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
     fi
 done
 
+cd "$PTEST_DIR"
+umount "$WORKDIR"
+rmdir "$WORKDIR"
-- 
2.34.1

Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Pratik Farkase]

Hi Paul,

I tried to report this upstream but issue creation is restricted on the libarchive GitHub repository here: 

https://github.com/libarchive/libarchive/issues

For the cd, since the script uses #!/bin/sh (pushd/popd aren't POSIX), Can i use
cd "$PTEST_DIR"? here. I have sent a v2 with this proposed fix.

Best Regards,
Pratik


________________________________________
From: Paul Barker
Sent: Monday, July 20, 2026 2:39 PM
To: Pratik Farkase; openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com
Subject: Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures


On Mon, 2026-07-20 at 14:26 +0200, Pratik Farkase wrote:
> The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
> including inode and device numbers. On ext4 root filesystems (particularly
> qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
> or newc 8-hex-digit field widths, causing intermittent assertion failures
> in test_format_newc and test_option_c.
> 
> Run all tests from a tmpfs working directory where inode numbers always
> start small, avoiding the overflow condition.
> 
> [YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Hi,

Has this issue been reported upstream to libarchive? It would be good to
get the test cases fixed so they can handle whatever inode numbers are
allocated.

> 
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
>  .../libarchive/libarchive/run-ptest              | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
> index d6b4c3f934..7f61e1b173 100755
> --- a/meta/recipes-extended/libarchive/libarchive/run-ptest
> +++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
> @@ -1,13 +1,24 @@
>  #!/bin/sh
>  
> +PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
> +
>  # The fuzz tests run 1000 randomised iterations per archive format and are
>  # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
>  # regularly time out in the time/memory constrained autobuilder QEMU targets
>  # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
>  export SKIP_TEST_FUZZ=1
>  
> +# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
> +# including inode and device numbers. On ext4 root filesystems inode numbers
> +# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
> +# field widths, causing intermittent assertion failures. Run all tests from
> +# a tmpfs where inode numbers start fresh and small.
> +WORKDIR=$(mktemp -d)
> +mount -t tmpfs tmpfs "$WORKDIR"
> +cd "$WORKDIR"
> +
>  for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
> -    ./$t
> +    "$PTEST_DIR"/$t
>      if [ $? -eq 0 ]; then
>          echo "PASS: $t"
>      else
> @@ -15,3 +26,6 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
>      fi
>  done
>  
> +cd /

It's better to use pushd/popd instead of finishing with `cd /`.

Best regards,

-- 
Paul Barker

Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Pratik Farkase]

Hi Paul,

Correction — I managed to file it upstream after all: https://github.com/libarchive/libarchive/issues/3314

Best Regards,
Pratik

________________________________________
From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> on behalf of Pratik Farkase via lists.openembedded.org <pratik.farkase=est.tech@lists.openembedded.org>
Sent: Monday, July 20, 2026 3:05 PM
To: Paul Barker; openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com
Subject: Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

Hi Paul,

I tried to report this upstream but issue creation is restricted on the libarchive GitHub repository here:

https://github.com/libarchive/libarchive/issues

For the cd, since the script uses #!/bin/sh (pushd/popd aren't POSIX), Can i use
cd "$PTEST_DIR"? here. I have sent a v2 with this proposed fix.

Best Regards,
Pratik


________________________________________
From: Paul Barker
Sent: Monday, July 20, 2026 2:39 PM
To: Pratik Farkase; openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com
Subject: Re: [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures


On Mon, 2026-07-20 at 14:26 +0200, Pratik Farkase wrote:
> The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
> including inode and device numbers. On ext4 root filesystems (particularly
> qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
> or newc 8-hex-digit field widths, causing intermittent assertion failures
> in test_format_newc and test_option_c.
>
> Run all tests from a tmpfs working directory where inode numbers always
> start small, avoiding the overflow condition.
>
> [YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Hi,

Has this issue been reported upstream to libarchive? It would be good to
get the test cases fixed so they can handle whatever inode numbers are
allocated.

>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
>  .../libarchive/libarchive/run-ptest              | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
> index d6b4c3f934..7f61e1b173 100755
> --- a/meta/recipes-extended/libarchive/libarchive/run-ptest
> +++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
> @@ -1,13 +1,24 @@
>  #!/bin/sh
> 
> +PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
> +
>  # The fuzz tests run 1000 randomised iterations per archive format and are
>  # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
>  # regularly time out in the time/memory constrained autobuilder QEMU targets
>  # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
>  export SKIP_TEST_FUZZ=1
> 
> +# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
> +# including inode and device numbers. On ext4 root filesystems inode numbers
> +# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
> +# field widths, causing intermittent assertion failures. Run all tests from
> +# a tmpfs where inode numbers start fresh and small.
> +WORKDIR=$(mktemp -d)
> +mount -t tmpfs tmpfs "$WORKDIR"
> +cd "$WORKDIR"
> +
>  for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
> -    ./$t
> +    "$PTEST_DIR"/$t
>      if [ $? -eq 0 ]; then
>          echo "PASS: $t"
>      else
> @@ -15,3 +26,6 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
>      fi
>  done
> 
> +cd /

It's better to use pushd/popd instead of finishing with `cd /`.

Best regards,

--
Paul Barker

Re: [OE-core][PATCH v2] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Mathieu Dubois-Briand]

On Mon Jul 20, 2026 at 2:58 PM CEST, Pratik Farkase wrote:
> The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
> including inode and device numbers. On ext4 root filesystems (particularly
> qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
> or newc 8-hex-digit field widths, causing intermittent assertion failures
> in test_format_newc and test_option_c.
>
> Run all tests from a tmpfs working directory where inode numbers always
> start small, avoiding the overflow condition.
>
> [YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---

Hi Pratik,

Thanks for the new version. It looks like we have some ptest failures
here:

Failed ptests:
{'libarchive': ['libarchive_test',
                'bsdtar_test',
                'bsdcpio_test',
                'bsdcat_test',
                'bsdunzip_test']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4107
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4091
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1981

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[OE-core][PATCH v3] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures

[Pratik Farkase]

The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
including inode and device numbers. On ext4 root filesystems (particularly
qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
or newc 8-hex-digit field widths, causing intermittent assertion failures
in test_format_newc and test_option_c.

Set TMPDIR to a tmpfs mount so the test framework creates its working
directories there, where inode numbers always start small.

[YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231

Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
Changes in v3:
- Use export TMPDIR instead of changing CWD (v2 broke test binary's
  ability to find reference data files)

Changes in v2:
- Use cd "$PTEST_DIR" instead of cd
---
 .../libarchive/libarchive/run-ptest                | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
index d6b4c3f934..f5f2ef490c 100755
--- a/meta/recipes-extended/libarchive/libarchive/run-ptest
+++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
@@ -1,11 +1,23 @@
 #!/bin/sh
 
+PTEST_DIR=$(cd "$(dirname "$0")" && pwd)
+cd "$PTEST_DIR"
+
 # The fuzz tests run 1000 randomised iterations per archive format and are
 # meant for dedicated fuzzing infrastructure, not routine ptest runs. They
 # regularly time out in the time/memory constrained autobuilder QEMU targets
 # (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
 export SKIP_TEST_FUZZ=1
 
+# The bsdcpio odc/newc format tests verify archive headers byte-by-byte
+# including inode and device numbers. On ext4 root filesystems inode numbers
+# can exceed the odc 6-octal-digit (262143) or newc 8-hex-digit (4294967295)
+# field widths, causing intermittent assertion failures. Set TMPDIR to a
+# tmpfs so test-created files get small inode numbers.
+WORKDIR=$(mktemp -d)
+mount -t tmpfs tmpfs "$WORKDIR"
+export TMPDIR="$WORKDIR"
+
 for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
     ./$t
     if [ $? -eq 0 ]; then
@@ -15,3 +27,5 @@ for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
     fi
 done
 
+umount "$WORKDIR"
+rmdir "$WORKDIR"
-- 
2.34.1