From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: virtio-fs@redhat.com, stefanha@redhat.com
Cc: vgoyal@redhat.com
Subject: [Virtio-fs] [PATCH] virtiofsd: Fix lo_destroy crash in g_hash_table_foreach_remove
Date: Wed, 7 Aug 2019 10:31:52 +0100 [thread overview]
Message-ID: <20190807093152.10964-1-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
This fixes a crash in lo_destroy since g_hash_table_foreach_remove
doesn't like the hashtable changing as it iterates, and unref_inode
will remove entries.
Avoid the g_hash_table_foreach_remove and use a dummy iterator to find
one element of the table at a time.
Fixes: virtiofsd: fix lo_destroy() resource leaks
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
---
contrib/virtiofsd/passthrough_ll.c | 27 +++++++++++++--------------
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/contrib/virtiofsd/passthrough_ll.c b/contrib/virtiofsd/passthrough_ll.c
index cc9c175047..321bbb20be 100644
--- a/contrib/virtiofsd/passthrough_ll.c
+++ b/contrib/virtiofsd/passthrough_ll.c
@@ -2445,18 +2445,6 @@ static void lo_removemapping(fuse_req_t req, struct fuse_session *se,
fuse_reply_err(req, ret);
}
-static int destroy_inode_cb(gpointer key, gpointer value, gpointer user_data)
-{
- struct lo_inode *inode = value;
- struct lo_data *lo = user_data;
-
- /* inode->nlookup is normally protected by lo->mutex but see the
- * comment in lo_destroy().
- */
- unref_inode(lo, inode, inode->nlookup);
- return TRUE;
-}
-
static void lo_destroy(void *userdata, struct fuse_session *se)
{
struct lo_data *lo = (struct lo_data*) userdata;
@@ -2474,10 +2462,21 @@ static void lo_destroy(void *userdata, struct fuse_session *se)
/* Normally lo->mutex must be taken when traversing lo->inodes but
* lo_destroy() is a serialized request so no races are possible here.
*
- * In addition, we cannot acquire lo->mutex since destroy_inode_cb() takes it
+ * In addition, we cannot acquire lo->mutex since unref_inode() takes it
* too and this would result in a recursive lock.
*/
- g_hash_table_foreach_remove(lo->inodes, destroy_inode_cb, lo);
+ while (true) {
+ GHashTableIter iter;
+ gpointer key, value;
+
+ g_hash_table_iter_init(&iter, lo->inodes);
+ if (!g_hash_table_iter_next(&iter, &key, &value)) {
+ break;
+ }
+
+ struct lo_inode *inode = value;
+ unref_inode(lo, inode, inode->nlookup);
+ }
}
static struct fuse_lowlevel_ops lo_oper = {
--
2.21.0
next reply other threads:[~2019-08-07 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 9:31 Dr. David Alan Gilbert (git) [this message]
2019-08-07 9:50 ` [Virtio-fs] [PATCH] virtiofsd: Fix lo_destroy crash in g_hash_table_foreach_remove Stefan Hajnoczi
2019-08-07 12:45 ` Vivek Goyal
2019-08-07 13:17 ` Dr. David Alan Gilbert
2019-08-07 13:29 ` Vivek Goyal
2019-08-08 9:45 ` Stefan Hajnoczi
2019-08-08 10:26 ` Dr. David Alan Gilbert
2019-08-09 8:27 ` Stefan Hajnoczi
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=20190807093152.10964-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.