linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: linux-cifs@vger.kernel.org, smfrench@gmail.com
Cc: ddiss@suse.de, aaptel@suse.com, Paulo Alcantara <pc@cjr.nz>,
	stable@vger.kernel.org
Subject: [PATCH] cifs: fix automount regression of dfs links
Date: Fri, 30 Apr 2021 15:08:43 -0300	[thread overview]
Message-ID: <20210430180843.16920-1-pc@cjr.nz> (raw)

Unfortunately we can't kfree() the UNC and prefix paths in
cifs_smb3_do_mount() because they could have come from a chased DFS
referral (automount) and we rely on the new values set in cifs_sb->ctx
prior to calling cifs_mount().

Instead, fix smb3_parse_devname() to not leak the UNC and prefix paths
when parsing new share paths.

Cc: <stable@vger.kernel.org> # v5.11+
Fixes: 315db9a05b7a ("cifs: fix leak in cifs_smb3_do_mount() ctx")
Signed-off-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
---
 fs/cifs/cifsfs.c     |  6 ------
 fs/cifs/connect.c    | 10 +++++++---
 fs/cifs/fs_context.c |  2 ++
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c
index 8a6894577697..bfe98136f9c1 100644
--- a/fs/cifs/cifsfs.c
+++ b/fs/cifs/cifsfs.c
@@ -863,12 +863,6 @@ cifs_smb3_do_mount(struct file_system_type *fs_type,
 		goto out;
 	}
 
-	/* cifs_setup_volume_info->smb3_parse_devname() redups UNC & prepath */
-	kfree(cifs_sb->ctx->UNC);
-	cifs_sb->ctx->UNC = NULL;
-	kfree(cifs_sb->ctx->prepath);
-	cifs_sb->ctx->prepath = NULL;
-
 	rc = cifs_setup_volume_info(cifs_sb->ctx, NULL, old_ctx->UNC);
 	if (rc) {
 		root = ERR_PTR(rc);
diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
index becd5f807787..ee4a92cbcb29 100644
--- a/fs/cifs/connect.c
+++ b/fs/cifs/connect.c
@@ -3159,9 +3159,13 @@ static int do_dfs_failover(const char *path, const char *full_path, struct cifs_
 int
 cifs_setup_volume_info(struct smb3_fs_context *ctx, const char *mntopts, const char *devname)
 {
-	int rc = 0;
+	int rc;
 
-	smb3_parse_devname(devname, ctx);
+	rc = smb3_parse_devname(devname, ctx);
+	if (rc) {
+		cifs_dbg(VFS, "%s: failed to parse %s: %d\n", __func__, devname, rc);
+		return rc;
+	}
 
 	if (mntopts) {
 		char *ip;
@@ -3189,7 +3193,7 @@ cifs_setup_volume_info(struct smb3_fs_context *ctx, const char *mntopts, const c
 		return -EINVAL;
 	}
 
-	return rc;
+	return 0;
 }
 
 static int
diff --git a/fs/cifs/fs_context.c b/fs/cifs/fs_context.c
index 1d6e0e15b034..b502a44e15a1 100644
--- a/fs/cifs/fs_context.c
+++ b/fs/cifs/fs_context.c
@@ -476,6 +476,7 @@ smb3_parse_devname(const char *devname, struct smb3_fs_context *ctx)
 
 	/* move "pos" up to delimiter or NULL */
 	pos += len;
+	kfree(ctx->UNC);
 	ctx->UNC = kstrndup(devname, pos - devname, GFP_KERNEL);
 	if (!ctx->UNC)
 		return -ENOMEM;
@@ -490,6 +491,7 @@ smb3_parse_devname(const char *devname, struct smb3_fs_context *ctx)
 	if (!*pos)
 		return 0;
 
+	kfree(ctx->prepath);
 	ctx->prepath = kstrdup(pos, GFP_KERNEL);
 	if (!ctx->prepath)
 		return -ENOMEM;
-- 
2.31.1


             reply	other threads:[~2021-04-30 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 18:08 Paulo Alcantara [this message]
2021-04-30 19:40 ` [PATCH] cifs: fix automount regression of dfs links Steve French
2021-04-30 20:56 ` Paulo Alcantara

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=20210430180843.16920-1-pc@cjr.nz \
    --to=pc@cjr.nz \
    --cc=aaptel@suse.com \
    --cc=ddiss@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stable@vger.kernel.org \
    /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).