From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Rob Herring <robh+dt@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v3 1/6] device property: Helper to match multiple connections
Date: Sun, 6 Mar 2022 20:18:24 -0600 [thread overview]
Message-ID: <YiVrcN3NA3uS0icv@yoga> (raw)
In-Reply-To: <YiIZoyfsJDcwR4gr@smile.fi.intel.com>
On Fri 04 Mar 07:52 CST 2022, Andy Shevchenko wrote:
> On Fri, Mar 04, 2022 at 03:41:33PM +0200, Sakari Ailus wrote:
> > On Fri, Mar 04, 2022 at 02:54:21PM +0200, Andy Shevchenko wrote:
> > > On Thu, Mar 03, 2022 at 02:33:46PM -0800, Bjorn Andersson wrote:
>
> ...
>
> > > > + if (count >= matches_len && matches) {
> > > > + fwnode_handle_put(ep);
> > > > + return count;
> > > > + }
> > >
> > > Wouldn't be the same as
> > >
> > > if (count >= matches_len) {
> > > fwnode_handle_put(ep);
> > > break;
> > > }
> >
> > Don't you need to check for non-NULL matches here?
>
> Right, this should be kept as in original patch.
>
> > I find return above easier to read.
>
> Okay, original code may work, so I have no strong opinion about return vs
> break, although I find slightly better to have a single point of return in
> such case.
>
I like using early returns when possible, but this is not an early
return and it is in the loop so it makes more sense to me to break out.
> > > ?
>
> ...
>
> > > > + count_graph = fwnode_graph_devcon_matches(fwnode, con_id, data, match,
> > > > + matches, matches_len);
> > >
> > > > + matches += count_graph;
> > > > + matches_len -= count_graph;
> > >
> > > No, won't work when matches == NULL.
> > >
> > > Also, matches_len is expected to be 0 in that case (or at least being ignored,
> > > check with vsnprintf() behaviour in similar case).
> > >
> > > So, something like this, perhaps
> > >
> > > if (matches && matches_len) {
> > > matches += count_graph;
> > > matches_len -= count_graph;
> > > }
> >
> > Good find!
>
> I have checked vsnprintf() and indeed, it expects to have the size is 0 when
> the resulting buffer pointer is NULL, and it doesn't do any additional checks.
>
Per the vsnprintf() semantics it's not the destination buffer being NULL
that's significant, but rather just the length being 0 that matters.
To follow that, I should fill @matches_len entries in @matches and then
just continue counting without storing anything in @matches.
But that won't work in this case, because in the event that the @match
function returns something that has to be freed (such as the refcounted
objects returned by the typec_mux code), dropping this in favor of just
counting it would cause memory/reference leaks.
As such, I think this should differ in that @matches = NULL is
significant, and it's nice to not have matches_len turn negative/bogus
in the count case.
So I like your suggestion.
Thanks,
Bjorn
> > > > + count_ref = fwnode_devcon_matches(fwnode, con_id, data, match,
> > > > + matches, matches_len);
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
next prev parent reply other threads:[~2022-03-07 2:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 22:33 [PATCH v3 1/6] device property: Helper to match multiple connections Bjorn Andersson
2022-03-03 22:33 ` [PATCH v3 2/6] device property: Use multi-connection matchers for single case Bjorn Andersson
2022-03-04 12:54 ` Andy Shevchenko
2022-03-03 22:33 ` [PATCH v3 3/6] typec: mux: Introduce indirection Bjorn Andersson
2022-03-04 12:58 ` Andy Shevchenko
2022-03-03 22:33 ` [PATCH v3 4/6] typec: mux: Allow multiple mux_devs per mux Bjorn Andersson
2022-03-04 13:54 ` Andy Shevchenko
2022-03-07 3:09 ` Bjorn Andersson
2022-03-03 22:33 ` [PATCH v3 5/6] dt-bindings: usb: Add binding for fcs,fsa4480 Bjorn Andersson
2022-03-03 22:33 ` [PATCH v3 6/6] usb: typec: mux: Add On Semi fsa4480 driver Bjorn Andersson
2022-03-04 12:54 ` [PATCH v3 1/6] device property: Helper to match multiple connections Andy Shevchenko
2022-03-04 13:41 ` Sakari Ailus
2022-03-04 13:52 ` Andy Shevchenko
2022-03-07 2:18 ` Bjorn Andersson [this message]
2022-03-07 9:31 ` Andy Shevchenko
2022-03-07 2:09 ` Bjorn Andersson
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=YiVrcN3NA3uS0icv@yoga \
--to=bjorn.andersson@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.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