From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: kishon@ti.com
Cc: lorenzo.pieralisi@arm.com, bhelgaas@google.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
andy.shevchenko@gmail.com,
Rolf Evers-Fischer <rolf.evers.fischer@aptiv.com>
Subject: [PATCH v3 1/2] pci: endpoint: Simplify name allocation for epf device
Date: Tue, 27 Feb 2018 11:02:29 +0100 [thread overview]
Message-ID: <20180227100231.22561-2-embedded24@evers-fischer.de> (raw)
In-Reply-To: <20180227100231.22561-1-embedded24@evers-fischer.de>
From: Rolf Evers-Fischer <rolf.evers.fischer@aptiv.com>
This commit replaces allocating and freeing the intermediate
'buf'/'func_name' with a combination of 'kstrndup()' and 'len'.
'len' is the required length of 'epf->name'.
'epf->name' should be either the first part of 'name' preceding the '.'
or the complete 'name', if there is no '.' in the name.
Signed-off-by: Rolf Evers-Fischer <rolf.evers.fischer@aptiv.com>
---
drivers/pci/endpoint/pci-epf-core.c | 22 ++++------------------
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/pci/endpoint/pci-epf-core.c b/drivers/pci/endpoint/pci-epf-core.c
index 766ce1dca2ec..1f2506f32bb9 100644
--- a/drivers/pci/endpoint/pci-epf-core.c
+++ b/drivers/pci/endpoint/pci-epf-core.c
@@ -200,8 +200,7 @@ struct pci_epf *pci_epf_create(const char *name)
int ret;
struct pci_epf *epf;
struct device *dev;
- char *func_name;
- char *buf;
+ int len;
epf = kzalloc(sizeof(*epf), GFP_KERNEL);
if (!epf) {
@@ -209,20 +208,11 @@ struct pci_epf *pci_epf_create(const char *name)
goto err_ret;
}
- buf = kstrdup(name, GFP_KERNEL);
- if (!buf) {
- ret = -ENOMEM;
- goto free_epf;
- }
-
- func_name = buf;
- buf = strchrnul(buf, '.');
- *buf = '\0';
-
- epf->name = kstrdup(func_name, GFP_KERNEL);
+ len = strchrnul(name, '.') - name;
+ epf->name = kstrndup(name, len, GFP_KERNEL);
if (!epf->name) {
ret = -ENOMEM;
- goto free_func_name;
+ goto free_epf;
}
dev = &epf->dev;
@@ -238,16 +228,12 @@ struct pci_epf *pci_epf_create(const char *name)
if (ret)
goto put_dev;
- kfree(func_name);
return epf;
put_dev:
put_device(dev);
kfree(epf->name);
-free_func_name:
- kfree(func_name);
-
free_epf:
kfree(epf);
--
2.16.2
next prev parent reply other threads:[~2018-02-27 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 10:02 [PATCH v3 0/2] pci: endpoint: Fix double free in pci_epf_create() Rolf Evers-Fischer
2018-02-27 10:02 ` Rolf Evers-Fischer [this message]
2018-02-27 10:09 ` [PATCH v3 1/2] pci: endpoint: Simplify name allocation for epf device Kishon Vijay Abraham I
2018-02-27 10:15 ` Rolf Evers-Fischer
2018-02-27 10:43 ` Kishon Vijay Abraham I
2018-02-27 10:02 ` [PATCH v3 2/2] pci: endpoint: Fix kernel panic after put_device() Rolf Evers-Fischer
2018-02-27 10:43 ` Kishon Vijay Abraham I
2018-02-27 17:57 ` Lorenzo Pieralisi
2018-02-28 10:29 ` Rolf Evers-Fischer
2018-02-27 10:20 ` [PATCH v3 0/2] pci: endpoint: Fix double free in pci_epf_create() Lorenzo Pieralisi
2018-02-27 12:11 ` Rolf Evers-Fischer
2018-02-27 14:52 ` Bjorn Helgaas
2018-02-28 10:35 ` Rolf Evers-Fischer
2018-02-27 16:13 ` Andy Shevchenko
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=20180227100231.22561-2-embedded24@evers-fischer.de \
--to=embedded24@evers-fischer.de \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rolf.evers.fischer@aptiv.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;
as well as URLs for NNTP newsgroup(s).