From: Markus Elfring <Markus.Elfring@web.de>
To: Ally Heev <allyheev@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Jonathan Corbet <corbet@lwn.net>,
Dan Carpenter <dan.carpenter@linaro.org>,
Dan Williams <dan.j.williams@intel.com>,
David Hunter <david.hunter.linux@gmail.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Nishanth Menon <nm@ti.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>
Subject: Re: [PATCH RESEND v3] checkpatch: add uninitialized pointer with __free attribute check
Date: Wed, 5 Nov 2025 10:18:12 +0100 [thread overview]
Message-ID: <221c2b9b-4809-48d8-af7d-f290d1c2a7fa@web.de> (raw)
In-Reply-To: <CAMuHMdV+12MoAGNHC9kf==Bt0cLuJ39Fs+W61DN67sE_p-u=og@mail.gmail.com>
…
> > +++ b/Documentation/dev-tools/checkpatch.rst
> > @@ -1009,6 +1009,11 @@ Functions and Variables
> >
> > return bar;
> >
> > + **UNINITIALIZED_PTR_WITH_FREE**
> > + Pointers with __free attribute should be initialized. Not doing so
> > + may lead to undefined behavior as the memory allocated (garbage,
> > + in case not initialized) to the pointer is freed automatically
> > + when the pointer goes out of scope.
>
> I think this is misleading, and can be improved: if the pointer is
> uninitialized, no memory was allocated?
* Do corresponding source code analysis requirements indicate a need
to perform data processing with other programming interfaces than regular expressions?
* How do you think about to mention the possibility once more that scopes
can be reduced for affected local variables?
https://elixir.bootlin.com/linux/v6.18-rc4/source/include/linux/cleanup.h#L142-L146
Regards,
Markus
next prev parent reply other threads:[~2025-11-05 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 9:56 Ally Heev
2025-11-04 13:28 ` Geert Uytterhoeven
2025-11-05 6:27 ` ally heev
2025-11-05 9:18 ` Markus Elfring [this message]
2025-11-06 16:29 ` ally heev
2025-11-06 17:03 ` [v3] " Markus Elfring
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=221c2b9b-4809-48d8-af7d-f290d1c2a7fa@web.de \
--to=markus.elfring@web.de \
--cc=allyheev@gmail.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=david.hunter.linux@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=geert@linux-m68k.org \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vireshk@kernel.org \
--cc=workflows@vger.kernel.org \
/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