From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: nenggun.kim@samsung.com, akpm@linux-foundation.org,
jh1009.sung@samsung.com, inki.dae@samsung.com, arnd@arndb.de,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: saa7134 fix media_dev alloc error path to not free when alloc fails
Date: Thu, 14 Apr 2016 18:08:58 -0300 [thread overview]
Message-ID: <20160414180858.43c8620b@recife.lan> (raw)
In-Reply-To: <1460651480-6935-1-git-send-email-shuahkh@osg.samsung.com>
Em Thu, 14 Apr 2016 10:31:20 -0600
Shuah Khan <shuahkh@osg.samsung.com> escreveu:
> media_dev alloc error path does kfree when alloc fails. Fix it to not call
> kfree when media_dev alloc fails.
No need. kfree(NULL) is OK.
Adding a label inside a conditional block is ugly.
>
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> ---
> drivers/media/pci/saa7134/saa7134-core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/pci/saa7134/saa7134-core.c b/drivers/media/pci/saa7134/saa7134-core.c
> index c0e1780..eab2684 100644
> --- a/drivers/media/pci/saa7134/saa7134-core.c
> +++ b/drivers/media/pci/saa7134/saa7134-core.c
> @@ -1046,7 +1046,7 @@ static int saa7134_initdev(struct pci_dev *pci_dev,
> dev->media_dev = kzalloc(sizeof(*dev->media_dev), GFP_KERNEL);
> if (!dev->media_dev) {
> err = -ENOMEM;
> - goto fail0;
> + goto media_dev_alloc_fail;
> }
> media_device_pci_init(dev->media_dev, pci_dev, dev->name);
> dev->v4l2_dev.mdev = dev->media_dev;
> @@ -1309,6 +1309,7 @@ static int saa7134_initdev(struct pci_dev *pci_dev,
> fail0:
> #ifdef CONFIG_MEDIA_CONTROLLER
> kfree(dev->media_dev);
> + media_dev_alloc_fail:
> #endif
> kfree(dev);
> return err;
--
Thanks,
Mauro
next prev parent reply other threads:[~2016-04-14 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 16:31 [PATCH] media: saa7134 fix media_dev alloc error path to not free when alloc fails Shuah Khan
2016-04-14 21:08 ` Mauro Carvalho Chehab [this message]
2016-04-14 22:18 ` Shuah Khan
2016-04-15 9:47 ` Mauro Carvalho Chehab
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=20160414180858.43c8620b@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=inki.dae@samsung.com \
--cc=jh1009.sung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nenggun.kim@samsung.com \
--cc=shuahkh@osg.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