LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erhard Furtner <erhard_f@mailbox.org>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test_bitmap fails on ppc/ppc64 on kernels v7.1.3, v7.2-rc2
Date: Wed, 8 Jul 2026 01:25:01 +0200	[thread overview]
Message-ID: <b9b762d0-cfe1-4fdb-b668-b6ef4afb0059@mailbox.org> (raw)
In-Reply-To: <98d65de7-e5aa-4197-85bd-219eab01e572@kernel.org>

>> test_bitmap: loaded.
>> test_bitmap: [lib/test_bitmap.c:397] bitmaps contents differ: expected 
>> "1,3-4,9", got "1,3-4,9,65-71,73-79,81-87,89-95,97-99"
>> test_bitmap: parselist('0-2047:128/256'):    912
>> test_bitmap: scnprintf("%*pbl", '0-32767'):    5977
>> test_bitmap: test_bitmap_read_perf:        1191082
>> test_bitmap: test_bitmap_write_perf:        1270153
>> test_bitmap: failed 1 out of 208655 tests
> 
> On QEMU (pmac32_defconfig) I get:
> 
> test_bitmap: loaded.
> test_bitmap: parselist('0-2047:128/256'):    2200
> test_bitmap: scnprintf("%*pbl", '0-32767'):    26440
> test_bitmap: test_bitmap_read_perf:        1819760
> test_bitmap: test_bitmap_write_perf:        18189840
> test_bitmap: all 208655 tests passed
> 
> On QEMU with your confirm I get:
> 
> [    1.162486] test_bitmap: loaded.
> [    1.177069] test_bitmap: [lib/test_bitmap.c:397] bitmaps contents 
> differ: expected "1,3-4,9", got "1,3-4,9,65-71,73-79,81-87,89-95,97-99"
> [    1.180599] test_bitmap: parselist('0-2047:128/256'):    2920
> [    1.190105] test_bitmap: scnprintf("%*pbl", '0-32767'):    65560
> [    1.427378] test_bitmap: test_bitmap_read_perf:        9546321
> [    1.438769] test_bitmap: test_bitmap_write_perf:        9344481
> [    1.457679] test_bitmap: failed 1 out of 208655 tests
> 
> So there is something with your config

Interesting! As I get the same test failure on my Talos II too.

Anyhow, I was able to bisect the issue. Offending commit is:

  # git bisect bad
6b5a4b68736798df1031404a2fad06d031253ef7 is the first bad commit
commit 6b5a4b68736798df1031404a2fad06d031253ef7 (HEAD)
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Thu Feb 26 12:16:44 2026 +0100

     bitmap: Add test for out-of-boundary modifications for scatter & gather

     Make sure that bitmap_scatter() and bitmap_gather() do not modify
     the bits outside of the given nbits span.

     Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
     Signed-off-by: Yury Norov <ynorov@nvidia.com>

  lib/test_bitmap.c | 10 +++++++---
  1 file changed, 7 insertions(+), 3 deletions(-)


Reverting this commit on top of v7.2-rc2 lets the test pass:

test_bitmap: loaded.
test_bitmap: parselist('0-2047:128/256'):	888
test_bitmap: scnprintf("%*pbl", '0-32767'):	6074
test_bitmap: test_bitmap_read_perf:		1190938
test_bitmap: test_bitmap_write_perf:		1259471
test_bitmap: all 208655 tests passed

Your hint about my config made me check a few options and I found the 
offending one, which is INIT_STACK_ALL_PATTERN=y. On a kernel built with 
INIT_STACK_ALL_ZERO=y the issue does not show up.

Regards,
Erhard


  reply	other threads:[~2026-07-07 23:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 19:27 test_bitmap fails on ppc/ppc64 on kernels v7.1.3, v7.2-rc2 Erhard Furtner
2026-07-07 22:29 ` Christophe Leroy (CS GROUP)
2026-07-07 23:25   ` Erhard Furtner [this message]
2026-07-08  7:43     ` Andy Shevchenko
2026-07-08  7:51       ` Christophe Leroy (CS GROUP)
2026-07-08 10:52         ` Andy Shevchenko
2026-07-08 16:48         ` Erhard Furtner

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=b9b762d0-cfe1-4fdb-b668-b6ef4afb0059@mailbox.org \
    --to=erhard_f@mailbox.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=chleroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox