linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2] btrfs: verify subvolid mount parameter
Date: Thu, 15 Feb 2018 01:11:37 +0800	[thread overview]
Message-ID: <20180214171137.5589-1-anand.jain@oracle.com> (raw)
In-Reply-To: <20180213161042.GV3003@twin.jikos.cz>

We aren't verifying the parameter passed to the subvolid mount option,
so we won't report and fail the mount if a junk value is specified for
example, -o subvolid=abc.
This patch verifies the subvolid option with match_u64.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
v1->v2:
 Title changed. Old:
   btrfs: manage subvolid mount option with match_u64
 Change log updated.
 keep the %s as token verification.

 fs/btrfs/super.c | 21 +++++++++------------
 1 file changed, 9 insertions(+), 12 deletions(-)

diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 10f7d0fbd50f..0333b8802a02 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -976,8 +976,8 @@ static int btrfs_parse_subvol_options(const char *options, fmode_t flags,
 {
 	substring_t args[MAX_OPT_ARGS];
 	char *opts, *orig, *p;
-	char *num = NULL;
 	int error = 0;
+	u64 subvolid;
 
 	if (!options)
 		return 0;
@@ -1007,18 +1007,15 @@ static int btrfs_parse_subvol_options(const char *options, fmode_t flags,
 			}
 			break;
 		case Opt_subvolid:
-			num = match_strdup(&args[0]);
-			if (num) {
-				*subvol_objectid = memparse(num, NULL);
-				kfree(num);
-				/* we want the original fs_tree */
-				if (!*subvol_objectid)
-					*subvol_objectid =
-						BTRFS_FS_TREE_OBJECTID;
-			} else {
-				error = -EINVAL;
+			error = match_u64(&args[0], &subvolid);
+			if (error)
 				goto out;
-			}
+
+			/* we want the original fs_tree */
+			if (subvolid == 0)
+				subvolid = BTRFS_FS_TREE_OBJECTID;
+
+			*subvol_objectid = subvolid;
 			break;
 		case Opt_subvolrootid:
 			pr_warn("BTRFS: 'subvolrootid' mount option is deprecated and has no effect\n");
-- 
2.15.0


  reply	other threads:[~2018-02-14 17:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  9:50 [PATCH] btrfs: manage thread_pool mount option as %u Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: manage subvolid " Anand Jain
2018-02-13 16:10   ` David Sterba
2018-02-14 17:11     ` Anand Jain [this message]
2018-02-23 22:08       ` [PATCH v2] btrfs: verify subvolid mount parameter David Sterba
2018-02-14 17:15     ` [PATCH] btrfs: manage subvolid mount option as %u Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: manage metadata_ratio " Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: manage check_int_print_mask " Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: manage commit " Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: add a comment to mark the deprecated mount option Anand Jain
2018-02-13  9:50 ` [PATCH] btrfs: fix bare unsigned declarations Anand Jain
2018-02-13 16:58   ` David Sterba
2018-02-14 17:13     ` [PATCH v2] " Anand Jain
2018-02-23 22:12       ` David Sterba
2018-02-26  8:46         ` [PATCH v3] " Anand Jain
2018-03-07 16:07           ` David Sterba
2018-02-13 14:26 ` [PATCH] btrfs: manage thread_pool mount option as %u Nikolay Borisov
2018-02-13 15:18   ` Anand Jain
2018-02-13 15:34     ` Nikolay Borisov
2018-02-13 15:58       ` David Sterba

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=20180214171137.5589-1-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@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).