From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Use resizable hash table for glocks
Date: Fri, 17 Jul 2015 09:49:41 -0400 (EDT) [thread overview]
Message-ID: <1441826102.40023485.1437140981704.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150715111349.GB16569@mwanda>
----- Original Message -----
> Hello Bob Peterson,
>
> The patch 6afe4c76af37: "GFS2: Use resizable hash table for glocks"
> from Mar 16, 2015, leads to the following static checker warning:
>
> fs/gfs2/glock.c:1798 gfs2_glock_iter_next()
> error: 'gi->gl' dereferencing possible ERR_PTR()
>
> fs/gfs2/glock.c
> 1793 static void gfs2_glock_iter_next(struct gfs2_glock_rht_iter *gi)
> 1794 {
> 1795 do {
> 1796 gi->gl = rhashtable_walk_next(&gi->hti);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> can return -EAGAIN sometimes.
>
> 1797 /* Skip entries for other sb and dead entries */
> 1798 } while ((gi->gl) && ((gi->sdp != gi->gl->gl_name.ln_sbd) ||
> ^^^^^^^^
> Might be an issue here, might not. I don't know the subsystem well
> enough to know when it returns NULL vs -EAGAIN.
>
> 1799
> __lockref_is_dead(&gi->gl->gl_lockref)));
> 1800 }
>
> regards,
> dan carpenter
>
Thanks, Dan. I'll craft a fix.
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2015-07-17 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 11:13 [Cluster-devel] GFS2: Use resizable hash table for glocks Dan Carpenter
2015-07-17 13:49 ` Bob Peterson [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=1441826102.40023485.1437140981704.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).