mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Teeple <keithrteeple@gmail.com>
To: szwyb123@gmail.com
Cc: akpm@linux-foundation.org, axboe@kernel.dk, david@davidgow.net,
	kunit-dev@googlegroups.com, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Keith Teeple <keithrteeple@gmail.com>
Subject: Re: [PATCH v2] lib/sbitmap: add KUnit test suite
Date: Wed, 21 Oct 2026 00:08:49 -0400	[thread overview]
Message-ID: <20261021040849.688374-1-keithrteeple@gmail.com> (raw)
In-Reply-To: <20261016073253.520971-1-szwyb123@gmail.com>

On Fri, 16 Oct 2026 15:32:53 +0800, Wang Yibo wrote:
> v2:
>  - Test sb.alloc_hint as a plain boolean: KUNIT_EXPECT_NOT_NULL() passes
>    its argument through a const void *, which a __percpu pointer cannot do
>    on architectures that keep percpu data in a separate address space, so
>    the test did not build on x86 (David Gow).
>  - Use a BITS_PER_LONG-relative bit number in sbitmap_test_iterate_set().
>    The hardcoded 130 lies past the end of the test bitmap when
>    BITS_PER_LONG is 32, so that bit was never visited and the test failed;
>    assert the precondition while at it (David Gow).

I am new here and trying to be helpful by testing others' patches. I
reproduced both v1 failures and confirmed the v2 fixes, applied on the
stated base (4056b3c9d3c9) and built with gcc 16.2.1:

  - x86_64 under QEMU: v1 fails to build at sbitmap_kunit.c:38,
    same as you saw with gcc 15.2. v2 builds and passes 8/8.

    One detail: this needs CONFIG_SMP=y as well as
    CONFIG_USE_X86_SEG_SUPPORT=y. Without SMP, __percpu has no address space and v1
    builds and passes. The kunit.py x64_64 QEMU config leaves SMP off by default.

  - i386 under QEMU: v1 fails sbitmap_test_iterate_set with
    nr_visited == 5 (expected 6). v2 passes 8/8.

  - UML: v2 passes 8/8.

Tested-by: Keith Teeple <keithrteeple@gmail.com>

      reply	other threads:[~2026-10-21  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  8:27 [PATCH] " Wang Yibo
2026-10-15 14:04 ` David Gow
2026-10-16  7:32   ` [PATCH v2] " Wang Yibo
2026-10-21  4:08     ` Keith Teeple [this message]

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=20261021040849.688374-1-keithrteeple@gmail.com \
    --to=keithrteeple@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=david@davidgow.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=szwyb123@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

all inboxes | Powered by JetHome®