public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumanth Korikkar <sumanthk@linux.ibm.com>
To: Chris Hofstaedtler <zeha@debian.org>
Cc: debian-loongarch@lists.debian.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, util-linux@vger.kernel.org,
	Karel Zak <kzak@redhat.com>
Subject: Re: [ANNOUNCE] util-linux v2.42-rc1
Date: Mon, 2 Mar 2026 10:16:51 +0100	[thread overview]
Message-ID: <aaVVg4PhVKkdL2C5@li-2b55cdcc-350b-11b2-a85c-a78bff51fc11.ibm.com> (raw)
In-Reply-To: <aaP6atFYpVqulTO1@zeha.at>

Hi Chris,

> Hi Sumanth, looong64 porters,
> 
> * Karel Zak <kzak@redhat.com> [260226 14:53]:
> > The util-linux release v2.42-rc1 is now available at
> >  http://www.kernel.org/pub/linux/utils/util-linux/v2.42/
> [..]
> > lsmem:
> >    - display global memmap on memory parameter (by Sumanth Korikkar)
> 
> It appears the test for this is run on looong64 and fails there (failing the
> entire build), at least in the Debian build infra.
> https://buildd.debian.org/status/fetch.php?pkg=util-linux&arch=loong64&ver=2.42%7Erc1-1&stamp=1772312955&raw=0
> 
> See below for log output excerpts.
> 
> Thanks,
> Chris
> 
> 
> log snippets:
> 
> ================= O/E diff ===================
> --- /build/reproducible-path/util-linux-2.42~rc1/tests/output/lsmem/lsmem-s390-zvm-6g	2026-02-28 21:08:31.577617951 +0000
> +++ /build/reproducible-path/util-linux-2.42~rc1/tests/expected/lsmem/lsmem-s390-zvm-6g	2026-02-18 11:33:47.804188659 +0000
> @@ -17,6 +17,7 @@
>  Memory block size:                256M
>  Total online memory:              4.8G
>  Total offline memory:             1.3G
> +Memmap on memory parameter:         no

The ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE feature is currently not enabled on
loong64.

The lsmem tool displays the setting found in
/sys/module/memory_hotplug/parameters/memmap_on_memory.  If this path
does not exist, lsmem will not show the parameter. As a result, the test
fails.

To resolve this, the test should first verify whether the file
/sys/module/memory_hotplug/parameters/memmap_on_memory exists. If it is
missing, the test should skip the output related to the "Memmap
on memory parameter". I will check how the test logic can be updated and
give it a try.

Thanks & Regards,
Sumanth


  reply	other threads:[~2026-03-02  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 12:53 [ANNOUNCE] util-linux v2.42-rc1 Karel Zak
2026-03-01  8:40 ` Chris Hofstaedtler
2026-03-02  9:16   ` Sumanth Korikkar [this message]
2026-03-02 15:59     ` Sumanth Korikkar
2026-03-22 11:37 ` unshare regression in 2.42-rc1 Chris Hofstaedtler
2026-03-22 12:57   ` Christian Albrecht Goeschel Ndjomouo
2026-03-26 14:01     ` Chris Hofstaedtler

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=aaVVg4PhVKkdL2C5@li-2b55cdcc-350b-11b2-a85c-a78bff51fc11.ibm.com \
    --to=sumanthk@linux.ibm.com \
    --cc=debian-loongarch@lists.debian.org \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux@vger.kernel.org \
    --cc=zeha@debian.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