public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
	Sasha Levin <sashal@kernel.org>
Cc: sandeen@redhat.com, v9fs@lists.linux.dev,
	linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] 9p: fix memory leak in v9fs_init_fs_context error path
Date: Tue, 03 Mar 2026 14:30:36 +0100	[thread overview]
Message-ID: <3398837.aeNJFYEL58@weasel> (raw)
In-Reply-To: <20260225135745.351984-1-sashal@kernel.org>

On Wednesday, 25 February 2026 14:57:45 CET Sasha Levin wrote:
> Move the assignments of fc->ops and fc->fs_private to right after the
> kzalloc, before any fallible operations. Previously these were assigned
> at the end of the function, after the kstrdup calls for uname and aname.
> If either kstrdup failed, the error path would set fc->need_free but
> leave fc->ops NULL, so put_fs_context() would never call v9fs_free_fc()
> to free the allocated context and any already-duplicated strings.
> 
> Fixes: 1f3e4142c0eb ("9p: convert to the new mount API")
> Assisted-by: Claude:claude-opus-4-6
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  fs/9p/vfs_super.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
 
> diff --git a/fs/9p/vfs_super.c b/fs/9p/vfs_super.c
> index 0a1c4f7cb001d..431f24938a1d3 100644
> --- a/fs/9p/vfs_super.c
> +++ b/fs/9p/vfs_super.c
> @@ -312,6 +312,9 @@ static int v9fs_init_fs_context(struct fs_context *fc)
>  	if (!ctx)
>  		return -ENOMEM;
> 
> +	fc->ops = &v9fs_context_ops;
> +	fc->fs_private = ctx;
> +
>  	/* initialize core options */
>  	ctx->session_opts.afid = ~0;
>  	ctx->session_opts.cache = CACHE_NONE;
> @@ -345,9 +348,6 @@ static int v9fs_init_fs_context(struct fs_context *fc)
>  	ctx->rdma_opts.timeout = P9_RDMA_TIMEOUT;
>  	ctx->rdma_opts.privport = false;
> 
> -	fc->ops = &v9fs_context_ops;
> -	fc->fs_private = ctx;
> -
>  	return 0;
>  error:
>  	fc->need_free = 1;



      parent reply	other threads:[~2026-03-03 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 13:57 [PATCH] 9p: fix memory leak in v9fs_init_fs_context error path Sasha Levin
2026-02-25 14:08 ` Dominique Martinet
2026-03-03 13:30 ` Christian Schoenebeck [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=3398837.aeNJFYEL58@weasel \
    --to=linux_oss@crudebyte.com \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=sandeen@redhat.com \
    --cc=sashal@kernel.org \
    --cc=v9fs@lists.linux.dev \
    /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