Linux Sound subsystem development
 help / color / mirror / Atom feed
From: David Hunter <david.hunter.linux@gmail.com>
To: hariconscious@gmail.com, perex@perex.cz, tiwai@suse.com
Cc: khalid@kernel.org, shuah@kernel.org, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/core/seq: Initialize structure pointer to NULL to prevent undefined behavior
Date: Sun, 5 Oct 2025 23:55:29 -0400	[thread overview]
Message-ID: <a6526df2-2861-4142-95e7-1c6a83321ac3@gmail.com> (raw)
In-Reply-To: <20251002174301.15512-1-hariconscious@gmail.com>

On 10/2/25 13:43, hariconscious@gmail.com wrote:
> From: HariKrishna Sagala <hariconscious@gmail.com>
> 
> This change ensures the structure pointer is explicitly initialized to
> NULL,preventing potential access to uninitialized memory. It improves
> code safety and avoids undefined behavior during pointer dereferencing.
> 
> Signed-off-by: HariKrishna Sagala <hariconscious@gmail.com>

Hi Harikrishna,

Thank you for detailing your attempt at testing. Unfortunately, your
patch makes no substantive change. The variable you are setting to NULL
is assigned before use, so there is no risk of undefined behavior.

I know this can seem discouraging to hear, but I do want you to
encourage you to keep looking for ways you can make contributions.

Thanks,
David

      parent reply	other threads:[~2025-10-06  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 17:43 [PATCH] sound/core/seq: Initialize structure pointer to NULL to prevent undefined behavior hariconscious
2025-10-03  7:21 ` Takashi Iwai
2025-10-06  3:55 ` David Hunter [this message]

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=a6526df2-2861-4142-95e7-1c6a83321ac3@gmail.com \
    --to=david.hunter.linux@gmail.com \
    --cc=hariconscious@gmail.com \
    --cc=khalid@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=shuah@kernel.org \
    --cc=tiwai@suse.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