From: Chris Hofstaedtler <zeha@debian.org>
To: Karel Zak <kzak@redhat.com>
Cc: Sumanth Korikkar <sumanthk@linux.ibm.com>,
debian-loongarch@lists.debian.org, util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.42-rc1
Date: Wed, 4 Mar 2026 14:34:28 +0100 [thread overview]
Message-ID: <aag0u2k9K3gr7XBa@zeha.at> (raw)
In-Reply-To: <pj7nqvgvazvimjhx7r3j7qt7zi2hvziv3bxjwnsaxpy45zjpxc@eimfo2zs6p5t>
* Karel Zak <kzak@redhat.com> [260303 11:09]:
>On Mon, Mar 02, 2026 at 04:59:06PM +0100, Sumanth Korikkar wrote:
>> * When --sysroot is used, do not read /sys/firmware/memory
>> (used on s390). This makes sure lsmem reads only the memory
>> directories inside the given sysroot, so the directory list
>> is correct.
>
>Thanks for looking into this. I think your patch is a workaround
>though. It bypasses sysmemconfig and memmap_on_memory when --sysroot
>is used rather than fixing the root cause.
>
>The real problem is that --sysroot prefix was not applied to all sysfs
>paths. The sysmemconfig handler was never prefixed, and print_summary()
>used raw fopen() to read memmap_on_memory, completely ignoring --sysroot.
>
>I've pushed different solution fix to
>https://github.com/util-linux/util-linux/pull/4090
Thanks, I've pulled this into our build and can confirm it fixes the
issue on loong64.
Best,
Chris
next prev parent reply other threads:[~2026-03-04 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:53 [ANNOUNCE] util-linux v2.42-rc1 Karel Zak
2026-02-27 0:28 ` Samuel Thibault
2026-03-03 11:46 ` Karel Zak
2026-03-03 13:13 ` Samuel Thibault
2026-03-01 8:40 ` Chris Hofstaedtler
2026-03-02 9:16 ` Sumanth Korikkar
2026-03-02 15:59 ` Sumanth Korikkar
2026-03-03 10:08 ` Karel Zak
2026-03-03 12:51 ` Sumanth Korikkar
2026-03-04 13:34 ` Chris Hofstaedtler [this message]
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
2026-03-29 10:54 ` 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=aag0u2k9K3gr7XBa@zeha.at \
--to=zeha@debian.org \
--cc=debian-loongarch@lists.debian.org \
--cc=kzak@redhat.com \
--cc=sumanthk@linux.ibm.com \
--cc=util-linux@vger.kernel.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