Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
	Mikhail Zaslonko <zaslonko@linux.ibm.com>
Cc: linux-s390@vger.kernel.org,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v2] s390/debug: Fix NULL pointer dereference in debug_info_copy()
Date: Tue, 22 Sep 2026 12:30:02 +0200	[thread overview]
Message-ID: <ecd27176-fce9-4a87-8f5a-3da9f3276985@linux.ibm.com> (raw)
In-Reply-To: <20260918104446.20386Dd4-hca@linux.ibm.com>

On 18.09.2026 12:44, Heiko Carstens wrote:
> On Wed, Sep 16, 2026 at 06:06:26PM +0200, Mikhail Zaslonko wrote:
>> When debug_register_static() fails, it clears areas, active_pages and
>> active_entries but leaves the area bounds unchanged. Copying such an
>> area, either by opening its view file or via debug_dump(), makes
>> debug_info_copy() dereference the NULL pointers.
>>
>> Skip the copy loop when the source has no areas.
>>
>> Closes: https://lore.kernel.org/r/20260903132123.12F271F00A3F@smtp.kernel.org
>> Fixes: d72541f94512 ("s390/debug: add early tracing support")
>> Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>
>> ---
>> v2:
>> - Different approach: check the areas pointer in debug_info_copy()
>>   instead of zeroing nr_areas/pages_per_area in debug_register_static().
>>   Zeroing nr_areas made debug_info_alloc() return ZERO_SIZE_PTR for
>>   active_pages/active_entries, which debug_to_act_entry() dereferences
>>   before debug_prev_entry() checks id->areas.
>>   Checking the pointer also matches what all other readers in this file
>>   already do.
>> - v1: https://lore.kernel.org/all/20260910104525.3788362-1-zaslonko@linux.ibm.com/
>>
>>  arch/s390/kernel/debug.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/s390/kernel/debug.c b/arch/s390/kernel/debug.c
>> index b5bf8284dbfc..d611d0eed1f6 100644
>> --- a/arch/s390/kernel/debug.c
>> +++ b/arch/s390/kernel/debug.c
>> @@ -434,7 +434,8 @@ static debug_info_t *debug_info_copy(debug_info_t *in, int mode)
>>  		debug_info_free(rc);
>>  	} while (1);
>>  
>> -	if (mode == NO_AREAS)
>> +	/* debug_register_static() failure leaves areas NULL, bounds intact */
>> +	if (mode == NO_AREAS || !in->areas)
> 
> This is just a more or less random indicator that debug_register_static()
> failed. But this seems to be the easiest way forward. Alternatively an
> explicit flag in debug_info_t would make this more obvious.
> 
> Anyway:
> Acked-by: Heiko Carstens <hca@linux.ibm.com>
> 
> Waiting for Peter's reply.

As Heiko mentioned, this can be done in a number of ways, but this one
is fine from my perspective.

Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>


-- 
Peter Oberparleiter
Linux on IBM Z Development - IBM Germany R&D

  reply	other threads:[~2026-09-22 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 16:06 [PATCH v2] s390/debug: Fix NULL pointer dereference in debug_info_copy() Mikhail Zaslonko
2026-09-16 16:16 ` sashiko-bot
2026-09-18 10:44 ` Heiko Carstens
2026-09-22 10:30   ` Peter Oberparleiter [this message]
2026-09-22 10:35 ` 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=ecd27176-fce9-4a87-8f5a-3da9f3276985@linux.ibm.com \
    --to=oberpar@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --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