From: Markus Elfring <Markus.Elfring@web.de>
To: Fei Shao <fshao@chromium.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Jerome Brunet <jbrunet@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [cocci] [v2] clk: Fix memory leak in devm_clk_notifier_register()
Date: Mon, 19 Jun 2023 11:43:42 +0200 [thread overview]
Message-ID: <45de3da1-42b9-8c08-9c7a-c84d0338acf3@web.de> (raw)
In-Reply-To: <CAC=S1njwxLfw7LcnXkgY7pbiFaqvNQVyAzHVhK9+nYJC63d=Zw@mail.gmail.com>
> > I can think of some ways to find this bug with static analysis.
>
> It was actually detected by kmemleak on an unreleased Chromebook device.
> I added the trace snippet in the message at first but removed that
> before sending this. Maybe I shouldn't have.
>
> I can resend a v3 to add that back if that's preferable. What do you think?
I find it helpful to add another bit of background information
for an improved change description.
Regards,
Markus
parent reply other threads:[~2023-06-19 9:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAC=S1njwxLfw7LcnXkgY7pbiFaqvNQVyAzHVhK9+nYJC63d=Zw@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=45de3da1-42b9-8c08-9c7a-c84d0338acf3@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=dan.carpenter@linaro.org \
--cc=fshao@chromium.org \
--cc=jbrunet@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).