From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Hangyu Hua <hbh25y@gmail.com>, miklos@szeredi.hu, vgoyal@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: fuse: dax: set fc->dax to NULL in fuse_dax_conn_free()
Date: Thu, 16 Nov 2023 16:52:23 +0800 [thread overview]
Message-ID: <345e0d5c-b01b-361d-fbb1-a0c6b093431e@linux.alibaba.com> (raw)
In-Reply-To: <20231116075726.28634-1-hbh25y@gmail.com>
On 11/16/23 3:57 PM, Hangyu Hua wrote:
> fuse_dax_conn_free() will be called when fuse_fill_super_common() fails
> after fuse_dax_conn_alloc(). Then deactivate_locked_super() in
> virtio_fs_get_tree() will call virtio_kill_sb() to release the discarded
> superblock. This will call fuse_dax_conn_free() again in fuse_conn_put(),
> resulting in a possible double free.
>
> Fixes: 1dd539577c42 ("virtiofs: add a mount option to enable dax")
> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> ---
> fs/fuse/dax.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/fuse/dax.c b/fs/fuse/dax.c
> index 23904a6a9a96..12ef91d170bb 100644
> --- a/fs/fuse/dax.c
> +++ b/fs/fuse/dax.c
> @@ -1222,6 +1222,7 @@ void fuse_dax_conn_free(struct fuse_conn *fc)
> if (fc->dax) {
> fuse_free_dax_mem_ranges(&fc->dax->free_ranges);
> kfree(fc->dax);
> + fc->dax = NULL;
> }
> }
>
--
Thanks,
Jingbo
next prev parent reply other threads:[~2023-11-16 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 7:57 Hangyu Hua
2023-11-16 8:52 ` Jingbo Xu [this message]
2023-11-30 10:54 ` Miklos Szeredi
2023-12-01 2:42 ` Hangyu Hua
2023-12-01 19:08 ` Vivek Goyal
2023-12-04 9:18 ` 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=345e0d5c-b01b-361d-fbb1-a0c6b093431e@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=hbh25y@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@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
all inboxes | Powered by JetHome®