From: Dan Carpenter <dan.carpenter@oracle.com>
To: mszeredi@redhat.com
Cc: linux-fsdevel@vger.kernel.org
Subject: [bug report] fuse: get rid of fuse_mount refcount
Date: Fri, 13 Nov 2020 12:00:49 +0300 [thread overview]
Message-ID: <20201113090049.GA95467@mwanda> (raw)
Hello Miklos Szeredi,
The patch 514b5e3ff45e: "fuse: get rid of fuse_mount refcount" from
Nov 11, 2020, leads to the following static checker warning:
fs/fuse/virtio_fs.c:1451 virtio_fs_get_tree()
error: double free of 'fm'
fs/fuse/virtio_fs.c
1418 if (!fs) {
1419 pr_info("virtio-fs: tag <%s> not found\n", fsc->source);
1420 return -EINVAL;
1421 }
1422
1423 err = -ENOMEM;
1424 fc = kzalloc(sizeof(struct fuse_conn), GFP_KERNEL);
1425 if (!fc)
1426 goto out_err;
1427
1428 fm = kzalloc(sizeof(struct fuse_mount), GFP_KERNEL);
1429 if (!fm)
1430 goto out_err;
1431
1432 fuse_conn_init(fc, fm, get_user_ns(current_user_ns()),
1433 &virtio_fs_fiq_ops, fs);
1434 fc->release = fuse_free_conn;
1435 fc->delete_stale = true;
1436 fc->auto_submounts = true;
1437
1438 fsc->s_fs_info = fm;
1439 sb = sget_fc(fsc, virtio_fs_test_super, set_anon_super_fc);
1440 if (fsc->s_fs_info) {
1441 fuse_conn_put(fc);
1442 kfree(fm);
^^^^^^^^^
Freed here
1443 }
1444 if (IS_ERR(sb))
1445 return PTR_ERR(sb);
1446
1447 if (!sb->s_root) {
1448 err = virtio_fs_fill_super(sb, fsc);
1449 if (err) {
1450 fuse_conn_put(fc);
1451 kfree(fm);
^^^^^^^^^
Double free
1452 sb->s_fs_info = NULL;
I'm sort of surprised this is setting "sb->" instead of "fsc->".
1453 deactivate_locked_super(sb);
1454 return err;
1455 }
1456
1457 sb->s_flags |= SB_ACTIVE;
1458 }
regards,
dan carpenter
next reply other threads:[~2020-11-13 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 9:00 Dan Carpenter [this message]
2020-11-13 10:08 ` [bug report] fuse: get rid of fuse_mount refcount Miklos Szeredi
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=20201113090049.GA95467@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@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.