From: Xiaomeng Tong <xiam0nd.tong@gmail.com>
To: viresh.kumar@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
nm@ti.com, sboyd@kernel.org, vireshk@kernel.org,
xiam0nd.tong@gmail.com
Subject: Re: [PATCH] opp: use list iterator only inside the loop
Date: Thu, 31 Mar 2022 10:20:09 +0800 [thread overview]
Message-ID: <20220331022009.28621-1-xiam0nd.tong@gmail.com> (raw)
In-Reply-To: <20220331021235.bhb4t2g43eva3c3s@vireshk-i7>
On Thu, 31 Mar 2022 07:42:35 +0530, Viresh Kumar wrote:
> Hi Xiaomeng,
>
> On 31-03-22, 09:58, Xiaomeng Tong wrote:
> > dev = new_dev->dev;
>
> Why is this added here ?
Sorry for that. I will delete it in next patch.
>
> >
> > As discussed before,
>
> Please remember that whatever you write here will go in the commit
> logs for ever and no one will ever know what you discussed and with
> whom.
>
> This area should describe the problem at hand.
>
ok, thank you for the suggestion.
> > we should avoid to use a list iterator variable
> > outside the loop which is considered harmful[1].
> >
> > In this case, use a new variable 'iter' as the list iterator, while
> > use the old variable 'new_dev' as a dedicated pointer to point to the
> > found entry.
> >
> > [1]: https://lkml.org/lkml/2022/2/17/1032
> >
> > Signed-off-by: Xiaomeng Tong <xiam0nd.tong@gmail.com>
> > ---
> > drivers/opp/debugfs.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/opp/debugfs.c b/drivers/opp/debugfs.c
> > index 596c185b5dda..a4476985e4ce 100644
> > --- a/drivers/opp/debugfs.c
> > +++ b/drivers/opp/debugfs.c
> > @@ -187,14 +187,19 @@ void opp_debug_register(struct opp_device *opp_dev, struct opp_table *opp_table)
> > static void opp_migrate_dentry(struct opp_device *opp_dev,
> > struct opp_table *opp_table)
> > {
> > - struct opp_device *new_dev;
> > + struct opp_device *new_dev = NULL, *iter;
> > const struct device *dev;
> > struct dentry *dentry;
> >
> > /* Look for next opp-dev */
> > - list_for_each_entry(new_dev, &opp_table->dev_list, node)
> > - if (new_dev != opp_dev)
> > + list_for_each_entry(iter, &opp_table->dev_list, node)
> > + if (iter != opp_dev) {
> > + new_dev = iter;
> > break;
> > + }
> > +
> > + if (!new_dev)
>
> I will rather make this BUG_ON(!new_dev);
>
Ok, i will take it.
> > + return;
> >
> > /* new_dev is guaranteed to be valid here */
> > dev = new_dev->dev;
--
Xiaomeng Tong
prev parent reply other threads:[~2022-03-31 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 1:58 Xiaomeng Tong
2022-03-31 2:12 ` Viresh Kumar
2022-03-31 2:20 ` Xiaomeng Tong [this message]
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=20220331022009.28621-1-xiam0nd.tong@gmail.com \
--to=xiam0nd.tong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/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
all inboxes | Powered by JetHome®