From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v2 3/4] driver property: constify property arrays values
Date: Wed, 1 Feb 2017 09:09:24 -0800 [thread overview]
Message-ID: <20170201170924.GA40045@dtor-ws> (raw)
In-Reply-To: <20170201144233.GN17297@lahna.fi.intel.com>
On Wed, Feb 01, 2017 at 04:42:33PM +0200, Mika Westerberg wrote:
> On Tue, Jan 31, 2017 at 06:11:29PM -0800, Dmitry Torokhov wrote:
> > Data that is fed into property arrays should not be modified, so let's mark
> > relevant pointers as const. This will allow us making source arrays as
> > const/__initconst.
> >
> > Also fix memory leaks on errors in property_entry_copy().
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> > drivers/base/property.c | 65 +++++++++++++++++++++++++++++++++---------------
> > include/linux/property.h | 12 ++++-----
> > 2 files changed, 51 insertions(+), 26 deletions(-)
> >
> > diff --git a/drivers/base/property.c b/drivers/base/property.c
> > index edc09854520b..fd91e0891665 100644
> > --- a/drivers/base/property.c
> > +++ b/drivers/base/property.c
> > @@ -682,44 +682,65 @@ int fwnode_property_match_string(struct fwnode_handle *fwnode,
> > }
> > EXPORT_SYMBOL_GPL(fwnode_property_match_string);
> >
> > +static int property_copy_string_array(struct property_entry *dst,
> > + const struct property_entry *src)
> > +{
> > + char **d;
> > + size_t nval = src->length / sizeof(*d);
> > + size_t i;
> > +
> > + d = kcalloc(nval, sizeof(*d), GFP_KERNEL);
> > + if (!d)
> > + return -ENOMEM;
> > +
> > + for (i = 0; i < nval; i++) {
> > + d[i] = kstrdup(src->pointer.str[i], GFP_KERNEL);
> > + if (!d[i] && src->pointer.str[i]) {
> > + while (--i >= 0)
> > + kfree(d[i]);
>
> Should we free d as well here?
Yep.
>
> > + return -ENOMEM;
> > + }
> > + }
> > +
> > + dst->pointer.str = (void *)d;
> > + return 0;
> > +}
--
Dmitry
next prev parent reply other threads:[~2017-02-01 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 2:11 [PATCH v2 0/4] Export APIs to copy device properties & more Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 1/4] device property: export code duplicating array of property entries Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 2/4] device property: allow to constify properties Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 3/4] driver property: constify property arrays values Dmitry Torokhov
2017-02-01 14:42 ` Mika Westerberg
2017-02-01 17:09 ` Dmitry Torokhov [this message]
2017-02-01 2:11 ` [PATCH v2 4/4] i2c: allow specify device properties in i2c_board_info Dmitry Torokhov
2017-02-01 15:24 ` Mika Westerberg
2017-02-01 17:10 ` Dmitry Torokhov
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=20170201170924.GA40045@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.