From: Andrew Morton <akpm@linux-foundation.org>
To: Mirsad Todorovac <mtodorovac69@gmail.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Jakob Koschel <jakobkoschel@gmail.com>,
Mike Rapoport <rppt@kernel.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
"Brian Johannesmeyer" <bjohannesmeyer@gmail.com>,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>,
Alexey Dobriyan <adobriyan@gmail.com>,
Yang Li <yang.lee@linux.alibaba.com>, Baoquan He <bhe@redhat.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Yan Zhen <yanzhen@vivo.com>
Subject: Re: [PATCH v1 1/1] fs/proc/kcore.c: fix coccinelle reported ERROR instances
Date: Tue, 29 Oct 2024 18:29:14 -0700 [thread overview]
Message-ID: <20241029182914.9006075cf5844bc8e679f72c@linux-foundation.org> (raw)
In-Reply-To: <20241029054651.86356-2-mtodorovac69@gmail.com>
On Tue, 29 Oct 2024 06:46:52 +0100 Mirsad Todorovac <mtodorovac69@gmail.com> wrote:
> Coccinelle complains about the nested reuse of the pointer `iter' with different
> pointer type:
>
> ./fs/proc/kcore.c:515:26-30: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:534:23-27: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:550:40-44: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:568:27-31: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:581:28-32: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:599:27-31: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:607:38-42: ERROR: invalid reference to the index variable of the iterator on line 499
> ./fs/proc/kcore.c:614:26-30: ERROR: invalid reference to the index variable of the iterator on line 499
>
> Replacing `struct kcore_list *iter' with `struct kcore_list *tmp' doesn't change the
> scope and the functionality is the same and coccinelle seems happy.
Well that's dumb of it. Still, the code is presently a bit weird and
we don't mind working around such third-party issues.
> NOTE: There was an issue with using `struct kcore_list *pos' as the nested iterator.
> The build did not work!
It worked for me. What's wrong with that?
> --- a/fs/proc/kcore.c
> +++ b/fs/proc/kcore.c
> @@ -493,13 +493,13 @@ static ssize_t read_kcore_iter(struct kiocb *iocb, struct iov_iter *iter)
> * the previous entry, search for a matching entry.
> */
> if (!m || start < m->addr || start >= m->addr + m->size) {
> - struct kcore_list *iter;
> + struct kcore_list *tmp;
`tmp' is a really poor identifier :(
Let's try `pos':
--- a/fs/proc/kcore.c~fs-proc-kcorec-fix-coccinelle-reported-error-instances-fix
+++ a/fs/proc/kcore.c
@@ -493,13 +493,13 @@ static ssize_t read_kcore_iter(struct ki
* the previous entry, search for a matching entry.
*/
if (!m || start < m->addr || start >= m->addr + m->size) {
- struct kcore_list *tmp;
+ struct kcore_list *pos;
m = NULL;
- list_for_each_entry(tmp, &kclist_head, list) {
- if (start >= tmp->addr &&
- start < tmp->addr + tmp->size) {
- m = tmp;
+ list_for_each_entry(pos, &kclist_head, list) {
+ if (start >= pos->addr &&
+ start < pos->addr + pos->size) {
+ m = pos;
break;
}
}
_
next prev parent reply other threads:[~2024-10-30 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 5:46 [PATCH v1 1/1] fs/proc/kcore.c: fix coccinelle reported ERROR instances Mirsad Todorovac
2024-10-30 1:29 ` Andrew Morton [this message]
2024-10-31 20:26 ` Mirsad Todorovac
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=20241029182914.9006075cf5844bc8e679f72c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=david@redhat.com \
--cc=h.j.bos@vu.nl \
--cc=hbathini@linux.ibm.com \
--cc=jakobkoschel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtodorovac69@gmail.com \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=yang.lee@linux.alibaba.com \
--cc=yanzhen@vivo.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