From: Dan Carpenter <dan.carpenter@oracle.com>
To: mszeredi@suse.cz
Cc: linux-fsdevel@vger.kernel.org
Subject: re: overlay filesystem
Date: Mon, 27 Oct 2014 16:54:49 +0300 [thread overview]
Message-ID: <20141027135449.GA2465@mwanda> (raw)
Hello Miklos Szeredi,
The patch e9be9d5e76e3: "overlay filesystem" from Oct 24, 2014, leads
to the following static checker warning:
fs/overlayfs/readdir.c:392 ovl_iterate()
warn: this array is probably non-NULL. 'p->name'
fs/overlayfs/readdir.c
387 while (od->cursor.l_node.next != &od->cache->entries) {
388 struct ovl_cache_entry *p;
389
390 p = list_entry(od->cursor.l_node.next, struct ovl_cache_entry, l_node);
391 /* Skip cursors */
392 if (p->name) {
^^^^^^^
The "Skip cursors" comment suggests that some other check was intended?
393 if (!p->is_whiteout) {
394 if (!dir_emit(ctx, p->name, p->len, p->ino, p->type))
395 break;
396 }
397 ctx->pos++;
398 }
399 list_move(&od->cursor.l_node, &p->l_node);
400 }
There are a couple others as well.
fs/overlayfs/readdir.c:254 ovl_dir_mark_whiteouts() warn: this array is probably non-NULL. 'p->name'
fs/overlayfs/readdir.c:319 ovl_seek_cursor() warn: this array is probably non-NULL. 'p->name'
regards,
dan carpenter
reply other threads:[~2014-10-27 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141027135449.GA2465@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@suse.cz \
/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).