From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Julian Braha <julianbraha@gmail.com>
Cc: gor@linux.ibm.com, hca@linux.ibm.com, iii@linux.ibm.com,
meted@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, akpm@linux-foundation.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] s390: fix dead defaults for S390_MODULES_SANITY_TEST and S390_UNWIND_SELFTEST
Date: Wed, 29 Apr 2026 16:42:03 +0200 [thread overview]
Message-ID: <a3adc8e8-ce4c-458c-a0c8-c0e66078589d-agordeev@linux.ibm.com> (raw)
In-Reply-To: <20260414215651.151228-1-julianbraha@gmail.com>
On Tue, Apr 14, 2026 at 10:56:51PM +0100, Julian Braha wrote:
> These config options currently have unconditional defaults of 'n' from the
> def_tristate statement, which shadow the later default of
> 'KUNIT_ALL_TESTS', causing it to be dead code.
>
> It looks to me like the commit 25d36a85c61b ("s390/test_unwind: convert to KUnit")
> added the KUNIT_ALL_TESTS default to S390_UNWIND_SELFTEST, but mistakenly
> didn't remove the previous 'n' default.
>
> Then, the later commit 90c5318795ee ("s390/module: test loading modules with a lot of relocations")
> copied the Kconfig layout from S390_UNWIND_SELFTEST when adding the
> S390_MODULES_SANITY_TEST config option, without noticing the existing mistake.
>
> This dead code was found by kconfirm, a static analysis tool for Kconfig.
This tool is still in development, right?
Anyway, I do not quite get what do you mean with the dead code.
Could you please elaborate?
> Fixes: 25d36a85c61b ("s390/test_unwind: convert to KUnit")
> Fixes: 90c5318795ee ("s390/module: test loading modules with a lot of relocations")
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
> arch/s390/Kconfig | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Thanks!
next prev parent reply other threads:[~2026-04-29 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 21:56 Julian Braha
2026-04-29 14:42 ` Alexander Gordeev [this message]
2026-04-29 21:39 ` Julian Braha
2026-05-06 12:37 ` Alexander Gordeev
2026-05-06 16:51 ` Julian Braha
2026-05-08 11:22 ` Alexander Gordeev
2026-05-08 12:35 ` Julian Braha
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=a3adc8e8-ce4c-458c-a0c8-c0e66078589d-agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=julianbraha@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=svens@linux.ibm.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®