From: Jakob Koschel <jakobkoschel@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Kumar Gala <galak@kernel.crashing.org>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Jakob Koschel <jakobkoschel@gmail.com>,
Anton Vorontsov <avorontsov@ru.mvista.com>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH] powerpc/sysdev: fix incorrect use to determine if list is empty
Date: Mon, 28 Feb 2022 15:24:33 +0100 [thread overview]
Message-ID: <20220228142434.576226-1-jakobkoschel@gmail.com> (raw)
'gtm' will *always* be set by list_for_each_entry().
It is incorrect to assume that the iterator value will be NULL if the
list is empty.
Instead of checking the pointer it should be checked if
the list is empty.
Fixes: 83ff9dcf375c ("powerpc/sysdev: implement FSL GTM support")
Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
---
arch/powerpc/sysdev/fsl_gtm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/sysdev/fsl_gtm.c b/arch/powerpc/sysdev/fsl_gtm.c
index 8963eaffb1b7..39186ad6b3c3 100644
--- a/arch/powerpc/sysdev/fsl_gtm.c
+++ b/arch/powerpc/sysdev/fsl_gtm.c
@@ -86,7 +86,7 @@ static LIST_HEAD(gtms);
*/
struct gtm_timer *gtm_get_timer16(void)
{
- struct gtm *gtm = NULL;
+ struct gtm *gtm;
int i;
list_for_each_entry(gtm, >ms, list_node) {
@@ -103,7 +103,7 @@ struct gtm_timer *gtm_get_timer16(void)
spin_unlock_irq(>m->lock);
}
- if (gtm)
+ if (!list_empty(>ms))
return ERR_PTR(-EBUSY);
return ERR_PTR(-ENODEV);
}
base-commit: 7ee022567bf9e2e0b3cd92461a2f4986ecc99673
--
2.25.1
next reply other threads:[~2022-02-28 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:24 Jakob Koschel [this message]
2022-03-08 12:07 ` [PATCH] powerpc/sysdev: fix incorrect use to determine if list is empty Michael Ellerman
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=20220228142434.576226-1-jakobkoschel@gmail.com \
--to=jakobkoschel@gmail.com \
--cc=avorontsov@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).