From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Erhard Furtner <erhard_f@mailbox.org>
Subject: Re: [PATCH] bitmap: Properly initialise destination bitmap for scatter & gather test
Date: Thu, 9 Jul 2026 14:53:18 +0300 [thread overview]
Message-ID: <ak-LroqSUcVMSSrZ@ashevche-desk.local> (raw)
In-Reply-To: <67d1838732b85b1f715cc3ada5bb38dcfcf9db55.1783593992.git.chleroy@kernel.org>
On Thu, Jul 09, 2026 at 01:40:06PM +0200, Christophe Leroy (CS GROUP) wrote:
> Erhard reports failure of bitmap tests on powerpc:
>
> 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
>
> The happens mainly when CONFIG_INIT_STACK_ALL_PATTERN is set.
>
> Commit 6b5a4b687367 ("bitmap: Add test for out-of-boundary
> modifications for scatter & gather") extended the test to
> out-of-boundary bits, but those bits where left uninitialised.
>
> Properly initialise the entire result bitmap before the test.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Thanks!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-09 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:40 [PATCH] bitmap: Properly initialise destination bitmap for scatter & gather test Christophe Leroy (CS GROUP)
2026-07-09 11:53 ` Andy Shevchenko [this message]
2026-07-09 17:31 ` Yury Norov
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=ak-LroqSUcVMSSrZ@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=erhard_f@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yury.norov@gmail.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