mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Zichen Xie <zichenxie0106@gmail.com>, linux-tegra@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Chenyuan Yang <chenyuan0y@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Sumit Gupta <sumitg@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Zijie Zhao <zzjas98@gmail.com>
Subject: Re: firmware: tegra: bpmp: Fix freeing uninitialized pointers
Date: Sat, 5 Oct 2024 18:35:09 +0200	[thread overview]
Message-ID: <5e798fd6-5662-48a3-8e3a-758f250828c8@web.de> (raw)
In-Reply-To: <CANdh5G4nX_PoRsWmCo1=TzoFA6k--29iJFgL-N_B_0anziAskg@mail.gmail.com>

> Thank you for the explanation and sorry for not realizing the correct
> deallocation function.
>
> I found in another email thread that the NULL initialization following
> the __free() was mainly for readability but not safety. Sorry for the
> confusion.
>
> We are working on a static analysis tool and wanted to report
> potential bugs. We directly sent a patch trying to reduce developer’s
> burden but didn’t not realize the correct use of Reported-by tag. We
> will be more careful in the future.

Please take another look at another corresponding public information source.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/researcher-guidelines.rst?h=v6.12-rc1#n5

Regards,
Markus

           reply	other threads:[~2024-10-05 16:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANdh5G4nX_PoRsWmCo1=TzoFA6k--29iJFgL-N_B_0anziAskg@mail.gmail.com>]

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=5e798fd6-5662-48a3-8e3a-758f250828c8@web.de \
    --to=markus.elfring@web.de \
    --cc=chenyuan0y@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=sumitg@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=zichenxie0106@gmail.com \
    --cc=zzjas98@gmail.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®