From: "Bumwoo Lee" <bw365.lee@samsung.com>
To: <myungjoo.ham@samsung.com>,
"'Chanwoo Choi'" <cw00.choi@samsung.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: RE: [PATCH v2 2/4] extcon: Added extcon_alloc_cables to simplify extcon register function
Date: Thu, 2 Mar 2023 17:33:12 +0900 [thread overview]
Message-ID: <006f01d94ce1$a0751300$e15f3900$@samsung.com> (raw)
In-Reply-To:
> -----Original Message-----
> From: Bumwoo Lee <bw365.lee@samsung.com>
> Sent: Thursday, March 2, 2023 4:12 PM
> To: 'myungjoo.ham@samsung.com' <myungjoo.ham@samsung.com>; 'Chanwoo Choi'
> <cw00.choi@samsung.com>; 'linux-kernel@vger.kernel.org' <linux-
> kernel@vger.kernel.org>
> Subject: RE: RE: [PATCH v2 2/4] extcon: Added extcon_alloc_cables to
> simplify extcon register function
>
>
> > -----Original Message-----
> > From: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Sent: Thursday, March 2, 2023 3:33 PM
> > To: Bumwoo Lee <bw365.lee@samsung.com>; Chanwoo Choi
> > <cw00.choi@samsung.com>; linux-kernel@vger.kernel.org
> > Subject: RE: RE: [PATCH v2 2/4] extcon: Added extcon_alloc_cables to
> > simplify extcon register function
> >
> > >
> > >
> > >--------- Original Message ---------
> > >Sender : 이범우 <bw365.lee@samsung.com>Product S/W Lab(VD)/삼성전자 Date :
> > >2023-03-02 10:38 (GMT+9) Title : RE: [PATCH v2 2/4] extcon: Added
> > >extcon_alloc_cables to simplify extcon register function
> > >
> > >Hello.
> > >
> > >As you can see, edev->cables are freed if extcon_alloc_cables()
> > >function return error handling in extcon_dev_register() Other added
> > functions are also same.
> > >
> > >Because it's functionalized, apart from this, do you want to mention
> > >that
> > it should be freed within the function?
> > >Please let me know your opinion.
> > >
> > >extcon_dev_register(struct extcon_dev *edev){ ...
> > >
> > > ret = extcon_alloc_cables(edev);
> > > if (ret)
> > > goto err_alloc_cables;
> > >
> > >...
> > >
> > >err_alloc_cables:
> > > if (edev->max_supported)
> > > kfree(edev->cables);
> > >
> > >
> > >Regards,
> > >Bumwoo
> >
> > In such a case, you are doing kfree(NULL); with the following:
>
> Yes, you are right.
> But Kfree() is checking NULL internally. So it does not a problem I think.
> Anyway I added kfree(edev->cables) before exit extcon_alloc_cables() like
> below on v3 patches.
>
> static int extcon_alloc_cables(struct extcon_dev *edev) { ...
> for (index--; index >= 0; index--) {
> cable = &edev->cables[index];
> kfree(cable->attr_g.name);
> }
>
> + kfree(edev->cables);
> return -ENOMEM;
> }
>
In order to avoid unnecessary kfree(NULL), the position will be moved like below on v4 patch.
err_alloc_muex:
for (index = 0; index < edev->max_supported; index++)
kfree(edev->cables[index].attr_g.name);
+ if (edev->max_supported)
+ kfree(edev->cables);
err_alloc_cables:
- if (edev->max_supported)
- kfree(edev->cables);
return ret;
> Regards,
> Bumwoo
next prev parent reply other threads:[~2023-03-02 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230220054545epcas1p4a2e170c1c67a675c6a54496417171d51@epcas1p4.samsung.com>
2023-02-20 5:45 ` [PATCH v2 0/4] Simplify extcon_dev_register function Bumwoo Lee
2023-02-20 5:45 ` [PATCH v2 1/4] extcon: Removed redundant null checking for class Bumwoo Lee
2023-02-20 5:45 ` [PATCH v2 2/4] extcon: Added extcon_alloc_cables to simplify extcon register function Bumwoo Lee
2023-02-24 10:03 ` MyungJoo Ham
2023-03-02 1:38 ` Bumwoo Lee
2023-03-02 3:44 ` Slade's Kernel Patch Bot
2023-03-02 6:33 ` MyungJoo Ham
2023-03-02 7:12 ` Bumwoo Lee
2023-03-02 8:33 ` Bumwoo Lee [this message]
2023-02-20 5:45 ` [PATCH v2 3/4] extcon: Added extcon_alloc_muex " Bumwoo Lee
2023-02-20 5:45 ` [PATCH v2 4/4] extcon: Added extcon_alloc_groups " Bumwoo Lee
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='006f01d94ce1$a0751300$e15f3900$@samsung.com' \
--to=bw365.lee@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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