Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mikhail Zaslonko" <zaslonko@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v2] s390/debug: Do not register views for failed static debug areas
Date: Fri, 18 Sep 2026 15:23:16 +0000	[thread overview]
Message-ID: <20260918152317.1CDC21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918151351.3977090-1-zaslonko@linux.ibm.com>

> __REGISTER_STATIC_DEBUG_INFO() calls debug_register_view()
> unconditionally, even when debug_register_static() has failed. In that
> case _debug_register() was never reached and id->debugfs_root_entry is
> still NULL, so debugfs_create_file() places the view file in the debugfs
> root directory. For sclp_err this leaves a /sys/kernel/debug/hex_ascii
> file with nothing to indicate which debug log it belongs to.
> 
> debug_register_static() is not exported and the macro is its only
> caller, so let it return an error code and skip the view registration
> when it fails. No debugfs files are created for such an area then.
> 
> Reproduce by booting with s390dbf=sclp_err::100000000. The sclp_err
> registration fails, no s390dbf/sclp_err/ directory is created, and a
> hex_ascii file appears in the debugfs root instead.
> 
> Fixes: d72541f94512 ("s390/debug: add early tracing support")
> Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918151351.3977090-1-zaslonko@linux.ibm.com?part=1


  reply	other threads:[~2026-09-18 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 15:13 [PATCH v2] s390/debug: Do not register views for failed static debug areas Mikhail Zaslonko
2026-09-18 15:23 ` sashiko-bot [this message]
2026-09-18 15:30 ` Heiko Carstens

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=20260918152317.1CDC21F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zaslonko@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