From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regmap: Properly free allocated name for regmap_config of syscon
Date: Wed, 11 Nov 2020 18:53:25 +0800 [thread overview]
Message-ID: <5660a879-2f11-c577-fe8e-0e1c6f244d8c@huawei.com> (raw)
In-Reply-To: <9b291d6ebdebe8a3a9f07d2bf4033fe9@kernel.org>
On 2020/11/10 16:47, Marc Zyngier wrote:
> On 2020-11-10 01:35, Kefeng Wang wrote:
>> On 2020/11/10 1:23, Mark Brown wrote:
>>> On Mon, Nov 09, 2020 at 07:58:16PM +0800, Kefeng Wang wrote:
>>>
>> Hi Marc, the regmap debugfs will duplicate a name in
>> regmap_set_name(), and
>>
>> syscon_config.name won't be used in syscon, so your following patch
>> doesn't seem
>>
>> to be necessary, right ? Please correct me if I'm wrong, thanks.
>
> It was certainly necessary at the time when I wrote the patch, as it
> was fixing some obvious memory corruption (use after free).
>
> It is very possible that the flow has been reorganised since, as the
> following commit hints at:
>
> commit e15d7f2b81d2e7d93115d46fa931b366c1cdebc2
> Author: Suman Anna <s-anna@ti.com>
> Date: Mon Jul 27 16:10:08 2020 -0500
>
> mfd: syscon: Use a unique name with regmap_config
>
> The DT node full name is currently being used in regmap_config
> which in turn is used to create the regmap debugfs directories.
> This name however is not guaranteed to be unique and the regmap
> debugfs registration can fail in the cases where the syscon nodes
> have the same unit-address but are present in different DT node
> hierarchies. Replace this logic using the syscon reg resource
> address instead (inspired from logic used while creating platform
> devices) to ensure a unique name is given for each syscon.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>
> I suggest you come up with a more complete analysis of the problem
> and how it came to be.
I check the history of above patch[1],
"The regmap name is expected to be managed by the caller and should be
live as long as the regmap is live, it is almost always static data."
so keep it as your patch said, thanks.
[1]
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20200727211008.24225-1-s-anna@ti.com/#23575471
>
> M.
prev parent reply other threads:[~2020-11-11 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 11:58 Kefeng Wang
2020-11-09 17:23 ` Mark Brown
2020-11-10 1:35 ` Kefeng Wang
2020-11-10 8:47 ` Marc Zyngier
2020-11-11 10:53 ` Kefeng Wang [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=5660a879-2f11-c577-fe8e-0e1c6f244d8c@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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
all inboxes | Powered by JetHome®